PluginUs.Net - Business Tools for WooCommerce and WordPress

[realize your idea - make your dreams come true]

Support Forum

You need to log-in to create request (topic) to the support

Search function and Husky

The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page please
If you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.

I have a search element on my website, and I'm looking for a solution where only relevant filters remain after a customer searches for a specific product.

However, the dynamic recounting and its cache are not functioning properly. When I enable dynamic recounting and clear the cache, the filter only retains the first filter menu. If a second query is entered, the filter menu still displays the options from the initial query.

Disabling the dynamic recounting cache slows down the website significantly. As a workaround, I've turned off the visibility of product counts.

The issue is that when customers continue their journey after searching, they end up with empty categories.

https://blijedieren.nl/z/product_cat-droogvoer-zaden/name-hondenvoer/?s=hondenvoer&post_type=product

Hello Jordy

Understood you, lets try some ways:

  • use it as you did but in tab Advanced enable"SEO URL request" and save, then clear all cache - this will create cache for results pages separately
  • also you can enable and use"Turbo mode" https://products-filter.com/extencion/turbo-mode/ and test it
  • also in tab Advanced -> Options ->"Cache terms" enable it to improve performance

Disabling the dynamic recounting cache slows down the website significantly - everything should be the other way around since dynamic recalculation eats up resources and disabling it, on the contrary, frees them up