Skip Navigation

[Resolved] problem with a custom search bar with filters

This support ticket is created 4 years, 9 months ago. 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.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 22 replies, has 3 voices.

Last updated by Christian Cox 4 years, 8 months ago.

Assisted by: Christian Cox.

Author
Posts
#1848739

yes exactly so I cannot use more than 9 filter for the search and I don't know what to do

#1848955

Okay I have escalated this issue to my 2nd tier support team for additional investigation. I'll let you know what I find out as soon as I have an update - most likely tomorrow.

#1849235

ok thanks waiting for this

#1849621

Our second tier team is investigating and I will provide an update as soon as I can.

#1852489

My 2nd tier support team has escalated this issue to our developers for further investigation, and I will continue to update you here as I receive more information.

#1853417

Our developers have recommended a change that will improve performance in this View. It turns out the post__not_in filter is somewhat expensive in queries, so you can disable it by unchecking the checkbox "Don't include the current page in the query result" in the View configurations. Our developers are working on a way to improve the performance of Views with many filters by disabling this query option when the post types do not match, but for now, unchecking the checkbox should significantly improve performance. Please try this workaround and let me know if the problem is not resolved.

#1860425

Our developers plan to include a more permanent solution for this issue in Blocks 1.4/Views 3.4. In the upcoming releases, performance will be improved by automatically limiting use of the post__not_in argument when the View's content and current post type are the same. I'll let you know once the new release is available for download.

#1861519

It turns out this issue has been addressed in the Blocks 1.3.3 release that is being pushed to the public today, as opposed to Blocks 1.4 as previously discussed. Please update to the latest versions of all Toolset plugins to receive the fix for this issue. If you have not yet been prompted to update on your site, you may need to go to Plugins > Add New, then click the "Commercial" tab to find the Toolset installer panel. Click "Check for updates" and the installer should find the latest version of Blocks and other plugins for download. To download the latest version of the Views plugin, you must go to https://toolset.com/account/downloads/#legacy-plugins

Let me know if the issue is not completely resolved after updating all Toolset plugins, and I'll be glad to take a closer look.