WP Solr not respecting Toolset views filters
2 years, 11 months ago #22462
Since activating WP Solr my Toolset views don’t work as they should, its like all the filter options and settings are ignored:
– Results are not based on my Toolset filters, e.g post type filters, custom filters based on custom fields set within a Toolset view.
– Show too many results, not the amount set in Tooslet views.
How can I fix this? Is there a setting to resolve this or is this a bug?
As soon as I deactivate the plugin my Toolset views filters etc work again.
Thanks2 years, 10 months ago #22465
No it is effecting all views. Archives appear to be working ok though.
Right now can’t keep the plugin enabled as it breaks every Toolset view.
If its a huge issue you could disable it making any changes on views and work just on archives? It doesn’t need to work on views.
Is there an option where I can set it just to work on archives and not views?
Matt2 years, 10 months ago #22469
Did you follow the guide https://www.wpsolr.com/guide/configuration-step-by-step-schematic/activate-extensions/toolset-views-add-on/ ?2 years, 10 months ago #22471
I did follow this guide but for “3) Select the archive types to speed up” I left this as just “search” but in hindsight I guess this was wrong, but CPTs are not showing here? Maybe I need to enable “Post types” as this is an option?
In regards to the views issues – I enabled debug in wp-config and this error started showing up on the actual pages where views are:
Notice: Trying to access array offset on value of type null in /home/stagingwowtrk/public_html/wp-content/plugins/wpsolr-pro/wpsolr/core/classes/extensions/suggestions/class-wpsolr-option-suggestions.php on line 1682 years, 10 months ago #22472
Can you try the fix on https://www.wpsolr.com/forums/topic/woocommerce-archive-pages-not-showing-products/page/3/ ?2 years, 10 months ago #22486
Thanks for this I have installed this version.
It seems like the queries of them are now working correctly but the limits set in the Toolset views are not being listened to.
Big improvement but still a huge issue that the result limits are being ignored.
With the Toolset archives, how can I tell if its being powered by WP Solr? I don’t have that many records yet so wasn’t that slow before (will have a lof of records in the next 1-2 weeks).
Cheers2 years, 10 months ago #22487
but the limits set in the Toolset views are not being listened to
What are these “limits”?
how can I tell if its being powered by WP Solr
In screen 2.1, you can activate the Elasticsearch debug mode. You’ll see the queries in your debug.log.
You can also delete your index content, check that results are empty, then re-index.2 years, 10 months ago #22491
So most views have an option to limit the results, see the screenshot below. We use this on most of our views. Also the query filter set in Toolset views is also not being respected even on the new version:
The initial content selection does now work though with this new version but limits and query filter does not.
Regarding checking if the search is being powered through WP Solr, I could not see any debug option in 2.1, I looked through all 2 options but couldn’t see anything? I did delete all the index though and the results were not empty for archives (they were for views), so seems like they are only working on views. To be honest if we can get it working correctly on one or the other (archives or views) I will be happy.
Right now though:
1) Archives are not being powered by WP Solr
2) Views limits and queries are not being respected.
Let me know what we can do.
You must be logged in to reply to this topic.