The page says "The filter set index is being built"
There is no index yet, and php-fpm does not have enough memory to build it (large catalog). Build it from the console: php @@core_path@@components/bitfacet/cli/rebuild.php <set>, and set up cron. Overview shows how much memory is needed.
The filter is not shown or "Filter set not found"
- Check the name in
&set. With &set=`auto` the page or its ancestor must be in the set's Sections (Products tab of the editor) — or the set has no sections.
- The snippet is called cached (
[[BitFacet]] instead of [[!BitFacet]]) — the filter "freezes".
- Filter errors — Index tab → Error log.
0 products, or a product is missing from the filter
- Preview — how many products are in the set; Products in the editor — do classes, templates, sections, contexts cut off too much?
- The product is unpublished or deleted — it is not on the site (that is expected).
- The product was changed bypassing MODX (SQL, external import) — Rebuild, or
queueChanged() from the import code.
A filter URL returns 404
- Friendly URLs on? Does the catalog page URL end with "/"? (Otherwise the filter uses parameters.)
- Is the
bitfacet.seo plugin enabled (OnPageNotFound event)?
- Is the value in the index? An old value no product has any more — 404. A SEO rule page without products — 404 as well.
Values repeat: "Nike", "NIKE", "Nike Inc"
BitFacet removes letter case and surrounding spaces itself. Merge different spellings on the Values tab → check → Merge. Product data is not changed.
Overview warns about opcache
The index does not fit into opcache memory, and BitFacet reads it from files — it works, but slower. Raise opcache.memory_consumption in PHP settings (on shared hosting — in the panel or via support); the warning says how much is needed.
I changed a setting but the site shows the old result
- Turbo mode is running — Overview → Clear cache.
- The set file was edited by hand — rebuild the index (saving in the manager does it itself).
- The page is cached by the browser or a CDN — reload without cache.
Turbo mode does not work
Settings → Turbo mode → Check connection:
- the socket does not answer — the service is not running:
systemctl status @@service@@, journalctl -u @@service@@ -n 50;
- through the site — 404 — the site's nginx has no
location = /bitfacet-turbo block;
- through the site — fallback — nginx cannot open the socket: the nginx user must be in the site user's group.
While turbo is down, the filter answers through the regular endpoint — the site keeps working.
A Fenom chunk is not handled in turbo mode
That is by design: turbo mode fills only simple chunks and passes other requests to the regular endpoint. For speed keep only [[+name]] and [[%key]] in chunks.