HUSKY Turbo Mode Not Working: Greyed-Out Filter and Missing Products
When HUSKY Turbo mode is not working, the symptoms look unrelated: the filter stays greyed out, a category returns no products, new products never appear, counts are wrong, or AJAX mode cannot be switched off. Almost all of them come from one design decision: in Turbo mode the filtering happens in the visitor's browser, against a file of product data built in advance. Below is how that file is made and used, and the fix for each symptom.
How Turbo mode works, and when it is worth using
In normal mode every filter click makes the server run a WooCommerce query and count the products for every term. Turbo mode moves that work to the browser. HUSKY writes all published products and their variations into one JSON file (by default in wp-content/uploads/uploads_woof_turbo_mode/) with the ID, title, SKU, prices, stock status, the terms of every product taxonomy and the values of Meta filter fields. The browser downloads it on every front-end page where the plugin runs (limit those pages with Init plugin on the next site pages only on the Advanced tab), finds the matching products and draws the counts; the server only renders the found products by their IDs.
So results are only as current as the file, a product missing from it cannot be found, only conditions the browser understands are applied, and every visitor downloads the whole catalog, which with tens of thousands of products and variations means megabytes and a slow start on phones. Turbo mode pays off on a weak server with a moderate catalog that changes rarely. If the server can run the queries, first try normal mode with the caches described in how to speed up product filtering in large catalogs.
Switch it on in the right order
- WooCommerce → Settings → Products Filter → Extensions: tick Turbo mode and save.
- Advanced → Turbo mode: set Enable turbo mode to Yes and save.
- Click Update now! under Reassemble products data now! and keep the page open until File updated!!! appears. Without the file, the filter cannot search.
- Choose the WordPress Cron period and Where to keep products data file, and save.
- In the Options tab set Show count, Dynamic recount and Hide empty terms, which in Turbo mode are separate copies (explained below), then purge the page cache and any CDN cache.
The filter is greyed out and never becomes clickable
The grey layer is an element with the class woof_turbo_mode_overlay. It covers the filter from the first moment, and the Turbo mode script removes it after the file has loaded and the counts are drawn. If the layer stays, that script did not finish:
- Scripts delayed, deferred or combined. Optimization features in WP Rocket, LiteSpeed Cache and similar plugins can start the scripts late, out of order or not at all. Turbo mode needs
ext/turbo_mode/js/turbo_mode.jsandext/quick_search/js/alasql/alasql.min.jsfromwp-content/plugins/woocommerce-products-filter/, after jQuery. Exclude the plugin folder from delay, defer and combine, then purge every cache; the filter with WP Rocket and caching explains the exclusions. - A JavaScript error. Open the browser console (F12) and reload. The first red error names the script that stopped the rest.
- A big file on a slow connection. In the Network tab, check the size and time of
data_0000_xxx.json. If the download keeps the filter grey for seconds, the catalog is too large for Turbo mode.
Hiding the layer with CSS (.woof_turbo_mode_overlay{display:none;}) only hides the symptom: the filter becomes clickable, but without a loaded file it cannot search.
When the file cannot be loaded, the filter is replaced by the notice Oh no! It looks like the filter can't open the search file. Check that:
- the file exists. A file kept in the plugin folder (plugins\woocommerce-products-filter\ext\turbo_mode\data) is deleted by every plugin update, so rebuild it after updates, or keep it in wp-uploads\uploads_woof_turbo_mode;
- no server rule or security plugin blocks
.jsonfiles in uploads: open the file address from the Network tab directly; - the address is right. The plugin requests
wp-content/uploads/uploads_woof_turbo_mode/, so on a multisite sub-site, or with the uploads folder moved elsewhere, the request returns 404. Keep the file in the plugin folder in that case.
No products found, or products missing after filtering
Turbo mode returns only products that are in the file, matched against the data stored there. Check both from the browser console, on a page with the filter, once it has loaded:
woof_turbo_mode_file.length // records in the file: products + variations
woof_turbo_mode_file.find(p => p.id == 123) // what is stored for product 123
Compare the first number with your published products plus variations; with WP-CLI, wp post list --post_type=product,product_variation --post_status=publish --format=count gives it. If a product returns undefined, it is not in the file. If it is there, look at its taxonomies and stock.
The file is out of date
New products, changed categories, attributes, prices and stock reach the filter only with the next rebuild. Typical signs: a new product is listed on the shop page but disappears after the first filter click, new terms show a count of 0, the last pagination pages are empty, or a Meta filter element added after the last rebuild finds nothing. Rebuild the file after imports and after changing the filter's elements.
The 15,000 limit
Update now! stops after 15,000 records, and variations count. A store with 2,000 variable products of eight variations each already has 18,000. The button processes the newest products first, so the products left out are your oldest ones. If the counter next to the button stopped at Products and Variants: 15000, you hit the limit. Raise it with the woof_turbo_mode_products_limit hook and rebuild:
/*
* HUSKY Turbo mode: let "Update now" write up to 40,000 products and variations.
* Child theme functions.php or a code snippets plugin.
*/
add_filter('woof_turbo_mode_products_limit', function ($limit) {
return 40000;
});
The scheduled rebuild is not capped by this hook; it processes the whole catalog.
Products in subcategories are not found
The file stores only the categories ticked on each product, and the browser compares them literally; it does not know the category tree. WordPress shows products of subcategories in a parent category, but Turbo mode does not: a product ticked only in Running shoes is listed on the Shoes page until the first filter click and then disappears, the Shoes filter term does not find it, and the Shoes count leaves it out. Tick every level of the chain (Shoes and Running shoes) on such products, for example with the bulk edit in Products → All Products, then rebuild the file.
Hidden and out-of-stock products
Products whose Catalog visibility is Shop only or Hidden count as hidden from search, and Turbo mode never returns them after filtering, whatever Listen catalog visibility says. A Shop only product therefore appears on the shop page and vanishes after the first click; set it to Shop and search results if it should be filterable. With WooCommerce's Hide out of stock items from the catalog enabled, out-of-stock products are left out of the file, and a product that comes back in stock stays missing until the next rebuild.
WPML languages
With WPML, HUSKY writes one file per language (data_0000_en.json, data_0000_de.json) and loads the file of the current language. A product without a translation is missing from that language's file, so rebuild after translating.
Keeping the search file up to date
Update now! builds the file in batches of ten products or variations, at most one batch per second, with a Products and Variants counter. Every batch rewrites the whole file, so 15,000 records take at least 25 minutes. Unlike the scheduled rebuild, the button deletes the current file first, and until it finishes the site filters with incomplete data: run it at a quiet time, keep the page open, and do not switch Turbo mode off in the middle.
WordPress Cron period sets the automatic rebuild: daily, weekly (the default), twicemonthly, monthly, min1 or without update. Despite the name, this is not a WP-Cron event. HUSKY keeps its own schedule (the option woof_turbo_init_wpcrone_): when a rebuild is due, each request that loads WordPress with the plugin, at most one every five seconds, adds the next ten records to a temporary file, which replaces the live file after the last batch. Visitors keep the previous data until then. What follows from that:
- WP Crontrol and similar tools do not list it, and
DISABLE_WP_CRONdoes not stop it. - Speed depends on requests that reach PHP; pages served from a page cache do not count. 20,000 records need at least 2,000 requests five seconds apart, close to three hours of steady traffic, and on a quiet site days.
- The first automatic rebuild comes one full period after you save the schedule, so click Update now! after enabling.
- The period counts from the end of the previous rebuild. min1 starts the next one a minute later, so the site rebuilds all the time; use it only for small catalogs.
- Update now! clicked during an automatic rebuild also deletes its temporary file; when the automatic run finishes, it replaces your complete file with the part it built afterwards. If products go missing again hours after a manual rebuild, click the button once more.
On a low-traffic site a server cron job can supply the requests; the FAQ why automatic cron updates fail shows the setup and PHP limits. Call it every minute, not once a day, because each call adds one batch. If you limited the plugin with Init plugin on the next site pages only, let it request /wp-admin/admin-ajax.php, where the plugin always loads. Even then it adds only 600 records per hour, so for catalogs that change in bulk, click Update now! after each import.
Other periods can be added with the woof_turbo_mode_schedules hook, without editing plugin files; then choose the new period and save:
/*
* HUSKY Turbo mode: add "every 12 hours" to WordPress Cron period.
* Child theme functions.php or a code snippets plugin.
*/
add_filter('woof_turbo_mode_schedules', function ($schedules) {
$schedules['every_12_hours'] = array(
'name' => 'every 12 hours',
'value' => 12 * HOUR_IN_SECONDS,
);
return $schedules;
});
The file keeps the same address after every rebuild. If a CDN or the browser caches .json files, visitors can keep receiving old data: exclude the uploads_woof_turbo_mode folder from CDN caching, or purge it after rebuilds.
Turbo mode needs AJAX and has its own count settings
While Turbo mode is enabled, HUSKY resets four settings on every page load: Try to ajaxify the shop becomes Yes, and the regular Show count, Dynamic recount and Hide empty terms become No. The Options tab then shows Turbo mode's own copies of these three under the same names, and Dynamic recount offers Yes, for all devices or Yes, only for PC.
- AJAX cannot be switched off while Turbo mode is on. Set Enable turbo mode to No, save, and only then change Try to ajaxify the shop.
- If the theme's product grid breaks after AJAX filtering (one product per row, lost columns, broken pagination), Turbo mode inherits it: see setting the column count in AJAX mode and pagination troubles in AJAX mode, or keep Turbo mode off for that theme.
- After switching Turbo mode off, set Show count, Dynamic recount and Hide empty terms again: they are still No, which is why counters vanish at that moment.
- Hide empty terms works only with Show count and Dynamic recount on; turning Show count off turns both others off.
- Cache dynamic recount number for each item in filter, Cache terms and Optimize price filter disappear from Advanced → Options while Turbo mode is on; they do not apply to it.
What Turbo mode cannot do
- The Hierarchy drop-down element does not work with it, as listed on the Turbo mode extension page.
- Counts and Hide empty terms work for the standard elements (checkbox, radio, drop-downs, colour, image, label, slider). Elements built with Smart Designer get no counts.
- In stock looks only at each product's own stock status; the setting that checks variations has no effect, so a filter by size can still show out-of-stock variations.
- Text search compares the typed words with product titles only, even if the text search element is set to look in descriptions or other fields. The separate SKU element works.
- Conditions added in PHP take no part in the search, because the browser decides which products match. Custom code on
woof_products_queryorpre_get_posts, custom extensions and plugins that limit products per vendor or customer group can at most hide some found products afterwards, which puts counts and pagination out of step.
If your store needs any of these, or its prices and stock change every hour, switch Turbo mode off and speed up normal mode with caching instead.
Checklist
- No red errors in the console; the plugin's scripts excluded from delay, defer and combine.
woof_turbo_mode_file.lengthmatches published products plus variations; the counter did not stop at the limit.- File rebuilt after the last import or filter change; page cache and CDN purged.
- Products ticked in the whole category chain, with Shop and search results visibility.
- Count settings set in Turbo mode's copies, and again after switching Turbo mode off.
If the filter still misbehaves, open a topic on the HUSKY support forum with the page link, the console errors, the value of woof_turbo_mode_file.length and the number of your products and variations.