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

cant hide terms and filters that are empty

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.

hey,

i have a eshop, using husky pro and astra pro template. all are full updated.

i have 4 taxonomies as filters: status (custom taxonomy), product category (from woocommerce), brand (from woocommerce) and age (custom taxonomy)

i expected empty terms to be hidden and also a whole filter to be hidden but it doenst happen. only the product categories work well.

in options i have set yes to: Show count, Dynamic recount, Hide empty terms

and also tried this: https://products-filter.com/how-to-hide-empty-counts

Hello

Thank you for the details.

First, please make sure you have the latest version of HUSKY installed. You can check the version in Plugins on your site.

Then please share a link to a page on your site where the problem is visible, so I can look at it directly. If you prefer to keep the link private, you can put it in the private section of this ticket, as shown in these screenshots:

https://share.pluginus.net/image/i20230222134241.png
https://share.pluginus.net/image/i20230222134615.png

In the meantime, please check caching. Dynamic recount and hiding empty terms are calculated on each request, so any cache can serve outdated term counts:

  1. Object cache (Redis, Memcached, or an object cache plugin) is the most likely cause. If you have one installed, please disable it temporarily and test again.
  2. Page/HTML cache (WP Rocket, LiteSpeed Cache, W3 Total Cache, hosting-level cache, etc.). Please clear it, or exclude the shop and category pages from caching, and test again.
  3. In HUSKY options, if “Cache dynamic recount” or “Cache terms” is enabled, please reset that cache too.

Let me know the results and the link, and I will continue from there.

Alex

hey,

this is the eshop: https://fiction.gr/shop/

sorry its in greek.

i've added credentials in the private data popup

also see this category, where category filter works as expected, but the other filters are not. https://fiction.gr/product-category/paichnidia/

 

Hello

Thank you for the links and the access. We noticed that the filter shows no product counts next to any term, even though Show count and Dynamic recount are enabled. Hiding empty terms depends on these counts, so this explains why the Status and Age filters keep showing all their terms. To see why the counts are not working, we need to look at the settings and the site from the inside.

Please do the following:

  1. Create a copy of your site on a test subdomain, for example with the Duplicator plugin, so your live shop is not touched.
  2. Put WP admin access to this test copy in the private area of this ticket.
  3. Place the actual purchase code of the plugin (from CodeCanyon or Freemius) in the private area of the ticket as well:

https://share.pluginus.net/image/i20230222134241.png
https://share.pluginus.net/image/i20230222134615.png
https://share.pluginus.net/image/i20230222134511.png

Once we have it, we will investigate the problem on the copy.

Kind regards, Alex

hey,

just put the creddentials .

thanx

Hello, thank you for the access; task is in the heap, we will provide you with an answer within the next day or two ...

Hello

Just tied to enter site today but I got:

fiction.gr took too long to respond.

Please check and give me know if its stable

hey,

maybe clear your cache?

i use the site all day with no issues.

we have updated php the day patches become public, thanx

Hello

Thank you. It is not the cache: I tested in Firefox, which I almost never use, so there was nothing cached there. The result is in the video:

https://drive.google.com/file/d/1dykUwxvXACCNgCSUjtLwdRb2SyvgmBPe/view?usp=sharing

This morning the site opened partly, but as soon as I open wp-admin/admin.php?page=wc-settings the page keeps loading and then the browser says the site is not reachable. Earlier today the server also answered me with 401 Unauthorized on the front pages.

Since the site works fine for you all day, the most likely reason is that the server limits or blocks requests coming from my side (Spain): a firewall or security plugin, rate limiting, or a country restriction for wp-admin. The other possible reason is the PHP update yesterday: after a PHP version change the PHP-FPM settings (max children, memory_limit, max_execution_time) are sometimes reset to defaults, and a heavy admin page like WooCommerce settings can then hang until it times out.

Could you or your host please check:

1. The server error log and PHP-FPM log for today, when I tried to open the site and wp-admin/admin.php?page=wc-settings.

2. Whether a firewall or security plugin has blocked or throttled my IP, and if so, whitelist it. I can send you my IP in the private area of this ticket.
3. The PHP-FPM limits and memory_limit after yesterday's update.

As soon as the admin opens normally for me, I will continue with the filter counts.

Kind regards, Alex

do you remember the httpasswd?

please give me your ip.

i just accessed the site through vpn (barcelona) and it works

php-fpm seems fine. also didnt find anything in logs.

hello,

just removed httpasswd for easier access.

best,

Hello

Thank you for removing the password protection and for checking the logs.

I tried again, but I still cannot work in the admin area of your site reliably, and this ticket has already taken too long for you. So let us do it another way, so that I do not depend on the connection to your server:

1. Install the free Duplicator plugin from Plugins, Add New.
2. Create a new backup (package) of the site. Duplicator produces two files: the archive (zip) and installer.php.
3. Upload both files to Google Drive (or any similar service) and share them with"Anyone with the link".
4. Put the link in the private section of this ticket, then write a short message here that it is done.

I will deploy the copy on my own server, find out what exactly blocks the counts and the hiding of empty terms, and then send you clear step by step instructions on what to change on your site.

Kind regards, Alex

hey,

just noticed this:

[26-Oct-2026 14:07:58 UTC] WordPress database error Table 'fiction_wordpress.wp_woof_front_builder' doesn't exist for query SELECT id FROM `wp_woof_front_builder` made by do_action('woocommerce_page_wc-settings'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Admin_Menus->settings_page, WC_Admin_Settings::output, include('/plugins/woocommerce/includes/admin/views/html-admin-settings.php'), do_action('woocommerce_settings_tabs_woof'), WP_Hook->do_action, WP_Hook->apply_filters, HUSKY->print_plugin_options, HUSKY->render_html_e, include('/plugins/woocommerce-products-filter/views/plugin_options.php'), do_action('woof_print_option_advanced'), WP_Hook->do_action, WP_Hook->apply_filters, WOOF_FRONT_BUILDER->global_options

maybe this is the problem?

duplicator as a solution, seems shady. we have to take clients permission for that.

 

hey,

just solved it.

i used the legacy widget. today i saw the shortcode generator and used that.

so probably legacy widget with astra template have some conflict.

thanx for your time

Hello

Great news, thank you for letting us know and for the detailed follow-up. You are right: the legacy widget is the old way of placing the filter, and the shortcode from the generator is the recommended one.

About the database error in the log: it is harmless and not related to the empty terms problem. It only appears because the Front Builder feature has never been used on your site.

For the future, if you run into any problem, the quickest way for us is the one we agreed on: a Duplicator copy of the site. We deploy it on our own server and do not depend on the connection to yours, so problems get solved much faster.

Kind regards, Alex