Quote from Alex Dev on May 20, 2026, 12:22

Hello Lazaros,

Thanks for the details and for sharing access. Two updates from my side before we continue:

First, the login credentials you placed in the private area do not work on my end. Please double-check them and update the private section so I can actually log in and look at the site directly.

Second, please update HUSKY to the latest build. I have placed the download link in the private area of this ticket. This is a fresh build that is not yet published on CodeCanyon and it contains several fixes related to WoodMart and to AJAX context handling that may already resolve part of what you are seeing. Start from the update before anything else.

Now to the analysis based on the URL you are filtering on (https://www.yoursite.gr/product-category/gearbox/?swoof=1&pa_gearbox-ratio=1031&really_curr_tax=471-product_cat):

1. Auto-opening filter blocks on WoodMart.

This is a known conflict between WoodMart and HUSKY. WoodMart ships its own JavaScript for handling sidebar widgets — it applies its own collapse/accordion logic and re-initializes widget state after the page finishes loading. HUSKY correctly renders the block as closed, then WoodMart's script runs later and forces it open. That is exactly the "blink then open" effect.

Try this on your side: in WoodMart theme settings, look for an option related to widget collapse or sidebar widget behavior (the exact wording varies between WoodMart versions, usually under Shop or Sidebar section). Disabling WoodMart's own widget collapse normally resolves this without custom code. If it does not, I will need access to inspect the actual markup WoodMart wraps around HUSKY blocks and add a targeted CSS or JS fix.

2. Redirect and empty results when filtering.

Looking at the URL above I can see two layered problems.

The first is the shortcode. You are using [woof redirect="" autosubmit=1 taxonomies=product_cat]. The taxonomies=product_cat parameter tells HUSKY to treat product_cat as a filterable taxonomy, which is the opposite of "stay inside the current category". Remove that parameter. If the filter is placed on a custom WPBakery page rather than the native category archive, also remember that HUSKY relies on the WooCommerce main query to detect the current category — on a custom builder page that context can be lost. The cleanest setup is to use HUSKY on the native category archive (widget in sidebar) so the context is picked up automatically.

The second is at WooCommerce level. Your Shop page and category archives are configured to display subcategories instead of products by default. As long as no filter is active, that is fine. But when WOOF starts filtering, WooCommerce still tries to show subcategories, and the filtered product list ends up either empty or redirected. The fix is to tell WooCommerce: "when a WOOF filter is running, switch to showing products". This is done with the snippet below. Add it to your child theme functions.php or a custom snippets plugin:

// Show products instead of categories when HUSKY filter is active
add_filter('option_woocommerce_shop_page_display', function($value) {
    if (function_exists('is_woof_search_going') AND is_woof_search_going()) {
        return '';
    }
    return $value;
});

add_filter('option_woocommerce_category_archive_display', function($value) {
    if (function_exists('is_woof_search_going') AND is_woof_search_going()) {
        return '';
    }
    return $value;
});

 

It uses HUSKY's built-in is_woof_search_going() helper to detect when a filter is active and overrides the display setting on the fly only for filtered requests. Normal browsing of category pages keeps showing subcategories as before.

So to move forward please do the following:

— Install the latest build from the link in the private area — Update the access credentials in the private area (the current ones do not work) — Remove taxonomies=product_cat from the shortcode — Try disabling WoodMart's widget collapse option — Add the snippet above to your child theme

Once the new access works I will log in, configure everything end to end, and confirm both the toggle state and the filtering behavior on the gearbox category.