[Résolu] view is filtered to a certain category, but search filter of cf shows all items
This support ticket is created Il y a 3 années et 8 mois. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
hey,
this view here, is filtered to show only products within a certain taxonomies:
hidden link
hidden link
(screen: the filtering section, limiting the view to one "super category" and one "brand")
I've added a search filter, dropdown style, to enable the user to pick a certain product within the initial filtering:
hidden link
(screen showing the filter of the custom field + showing the option of "Show only available options for each input" enabled)
but in the frontend, the dropdown shows ALL products and not just products in the certain "super category" and "brand": hidden link
(screen showing the dropdown showing all products)
no - wait - doesn't work. but strangely it works if I add a THIRD view with same filters, except the two custom fields filters... check out the view with ID 21723
Even after testing with a couple of different servers and PHP versions, I couldn't reproduce this issue on a clean install. This suggests that something specific to your website is involved.
The "/compare-food-processors/" page on your website seems to have been moved. Can you please make sure that all plugins are updated to the latest versions and share a clone/snapshot of the website?
( ref: https://toolset.com/faq/provide-supporters-copy-site/ )
Please also share a link to a page where this issue can be seen. This way, I'll be able to investigate this in more depth on my own server, without affecting the actual live website.
I tried to create a duplicator package of your website too, but it didn't work, even after excluding the "uploads" folder and with only database option enabled.
Tip: This plugin also allows excluding "media library" items from the package, which would reduce the size exponentially.
In case, it doesn't work, you can share a ".sql" export file of the database from a database management tool like phpMyAdmin and share the web site's files (excluding the "uploads" folder) in a zip file separately.
During troubleshooting on your website's clone, I noticed that the issue of the irrelevant options showing in the search filters gets fixed if the Elementor Pro plugin is deactivated.
I'll recommend updating WordPress, active theme and all plugins to the latest versions and clear all involved caches and then check the search filter dropdown again.
Despite switching to default Twenty Twenty theme and removing all plugins other than Toolset and WooCommerce, the issue with the custom field's search dropdown persisted on your website's clone.
Since this behavior is not reproducible on a clean/new installs, I've shared this with the concerned team as an exception, for further review.
I'll keep you updated with the progress through this ticket.
Thank you for waiting and I've heard back from the concerned team.
That option ( "Show only available options for each input" ) requires a reasonably expensive query. In Blocks, it even comes with a warning, although we don’t have it in classic Views.
( screenshot: hidden link )
On your website, the "wp_postmeta" table is *extremely* large, at 66Mb and it is entirely expected that problems arise when filtering by custom fields and this option enabled.
Moving forward, we have two recommendations:
1. Whenever possible, use taxonomies instead of custom fields for filtering posts. Filtering posts by custom fields are in general a bad idea as it is not optimized in the way that filtering by taxonomies is. Here’s a good link explaining the problem: hidden link
2. For cases, where the post-filtering by custom field is unavoidable and the website has a large number of posts and custom fields, it is better to keep that option disabled.
