[wpsolr]

6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18770

The table “wp_wpsolr_index_history” is used for indexing product taxonomies only that will be shown in WPSOLR suggestions. It’s normal then that WPSOLR tries to create it when you select some in 2.2

What is not normal is the SQL error.

[wpsolr]

6 years, 6 months ago in reply to: Site with archived content #18768

Why would you move your older posts?

[wpsolr]

6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18739

Strange.

Try in screen 2.2 to select only post types to index.

[wpsolr]

6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18738

I do not understand why you get so many results on one single query. The pagination size in screen 2.2 should limit the results to 20 or something around.

[wpsolr]

6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18732

“DROP TABLE wp_wpsolr_index_history;” should fix the problem.

[wpsolr]

6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18729

The beta is for sitemaps only, because of a limitation of Google’s maximum number of files in a sitemaps (less files means more links in a file, sometimes more than 10K).
But for category products, you should have a pagination to limit the number of results fetched.

For facets, they should not be affected by the number of results. Clients’ sites with 500K products or a million listings can display all facets. Perhaps you can increase the option “No. of values to be displayed by filters” in screen 2.1?

[wpsolr]

6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18726

I added Elasticsearch scroll in the latest beta release, to be able to generate huge Yoast sitemaps (million+).

What would be your need?

[wpsolr]

6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18724

Do you mean like https://stackoverflow.com/questions/41655913/elk-how-do-i-retrieve-more-than-10000-results-events-in-elastic-search ?

[wpsolr]

6 years, 6 months ago in reply to: cannot build index #18709

It is not possible to prevent product descriptions to be indexed.

[wpsolr]

6 years, 6 months ago in reply to: cannot build index #18705

The debug shows that 184073,184086 are excluded from the index, as they should.

If you look further in the debug message, you will find the details of the product currently indexed with the error.

[wpsolr]

6 years, 6 months ago in reply to: cannot build index #18700

What makes you think the search pages are indexed?

[wpsolr]

6 years, 6 months ago in reply to: cannot build index #18698

Edit the page, and check the WPSOLR meta box “Do not search”. The page will not be indexed.

[wpsolr]

6 years, 6 months ago in reply to: cannot build index #18695

Yes, your limit of 10K could be a long-term problem:
https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/in-depth/index-and-records-size-and-usage-limitations/

Your other indexes are probably replicas of your main index, created automatically by WPSOLR to perform sorts. In Algolia, each sorted field requires its own index for performance/optimisation reasons:
https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/#backend-implementation-replicas

• This reply was modified 6 years, 6 months ago by wpsolr.

[wpsolr]

6 years, 6 months ago in reply to: cannot build index #18693

If you uncheck option “Index custom fields” in screen 2.2, your custom fields will not be added to your document content. You’ll need then to reindex all your documents.

[wpsolr]

6 years, 6 months ago in reply to: cannot build index #18690

For your indexing issue, you can ask Algolia’s support to check your last batch index logs. The indexed data is logged at Algolia, just ask them why you get the UTF-8 encoding error.

You can also try to index with the test Elasticsearch index instead of Algolia.