Forum Replies Created
-
wpsolrKeymaster6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18884
What is your WPSOLR version?
wpsolrKeymaster6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18855Can you delete the WP option ‘wdm_db’? It controls the table creation vs alter.
wpsolrKeymaster6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18854I don’t understand how, if the table does not exist yet, the delta sql tries to alter the table?
wpsolrKeymaster6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18850This table is filled only when you index taxonomies on their own (to be displayed in suggestions). In 2.2, you should select the taxonomies at the same level as the pos types.
wpsolrKeymaster6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18844Good idea. I moved the topic in “New feature requests” forum.
wpsolrKeymaster6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18823It could be due to a breaking change for Elasticsearch 7, which returns 10,000 total documents maximum, unless track-total-hits is set on each query:
https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-7.0.html#track-total-hits-10000-defaultwpsolrKeymaster6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18822Clients with the same WPSOLR as yours can display hundreds of thousands of results. No need of Elasticsearch cursors. Cursors are only useful for paginating above 10K results (displaying search page 1000, if a page contains 10 results). But you are showing page 1.
wpsolrKeymaster6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18819@maxwatson Can you show me exactly the problem in a screenshot?
wpsolrKeymaster6 years, 6 months ago in reply to: Site with archived content #18817Please use the pricing page booking button if you want to discuss some custom work.
- This reply was modified 6 years, 6 months ago by wpsolr.
wpsolrKeymaster6 years, 6 months ago in reply to: Support for all WP query’s #18783I’ll fix the custom post type status admin search in next release.
REST API is not taken care by WPSOLR.
wpsolrKeymaster6 years, 6 months ago in reply to: Site with archived content #18782There is no generic method. Its theme by theme.
wpsolrKeymaster6 years, 6 months ago in reply to: WordPress database error on step 2.2 #18779If you index some categories, this table should be filled automatically.
wpsolrKeymaster6 years, 6 months ago in reply to: Remove 10000 limit when using elasticsearch #18778“Also in tab 2.1 Replace front-end archives I’ve checked only Search, but it applies the query to product categories also, is this normal?”
Because “Replace categories search” is selected on the WPSOLR WooCommerce extension?wpsolrKeymaster6 years, 6 months ago in reply to: Site with archived content #18777Only main archive queries are replaced by WPSOLR. This is why we built some add-ons for themes like Listify, Jobify, Mylisting, Directory+, Listable.
You can check with https://wordpress.org/plugins/query-monitor/
wpsolrKeymaster6 years, 6 months ago in reply to: Support for all WP query’s #18776Did you select “Index all statuses” for your post type on screen 2.2?