# PrestaShop category page filters have disappeared

> Filters by price, brand or feature that showed yesterday and don’t today: they rely on the faceted search module and a cache that needs rebuilding after any significant catalogue change. In most cases, regenerating that cache from the module’s settings brings them straight back.

- Source canonique : [https://allaux.fr/en/prestashop/problemes/filtres-page-categorie-disparus](https://allaux.fr/en/prestashop/problemes/filtres-page-categorie-disparus)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> Open Modules > Module Manager, go into the configuration of ps_facetedsearch and run the filter index rebuild: it regenerates the list of criteria available for each category after products or attributes have been added. Then check the module is still hooked on the theme’s displayLeftColumn or displayRightColumn.

## Why filters depend on a separate module and cache

On a category page, filters by price, brand, attribute or feature don’t come from each product record read live: they’re generated by the faceted search module, ps_facetedsearch on a standard install. This module pre-builds the list of available filters for each category and stores it in a cache.

That cache needs rebuilding whenever the catalogue changes significantly: new products, a new attribute, an edited feature. A dedicated setting, in the module’s own preferences or under Preferences > Search, forces this rebuild.

## Why the filters have disappeared

- The faceted search module was disabled by mistake during a theme or PrestaShop update.
- An attribute or feature isn’t ticked “used in filters” on the product record.
- The filter cache wasn’t rebuilt after a bulk import or a large batch of new products.
- A theme module customising the category page layout hides the filter block without actually disabling the module behind it.

## A setting to tick, or a filter to build

> Re-ticking an attribute, re-enabling the module, or rebuilding the cache solves the large majority of cases. A filter on a field that doesn’t exist natively in PrestaShop, such as a criterion specific to one line of business, needs a custom extension of the filter module instead.

## Related pages

- **Internal search not finding certain products** — A related issue, but one affecting the search bar’s keyword index, not category filters. ([/prestashop/problemes/recherche-interne-ne-trouve-pas-produits](/prestashop/problemes/recherche-interne-ne-trouve-pas-produits))
- **Bulk-importing products via CSV** — A large import is often what makes rebuilding the filter cache necessary. ([/prestashop/problemes/import-produits-masse-csv](/prestashop/problemes/import-produits-masse-csv))
- **PrestaShop store slow to load** — A filter cache that’s never rebuilt can also slow down category page rendering. ([/prestashop/boutique-lente](/prestashop/boutique-lente))
- **Custom PrestaShop module development** — For a filter on a custom field the native module can’t handle. ([/prestashop/module-sur-mesure](/prestashop/module-sur-mesure))

## FAQ

### Why has a brand filter disappeared when the brands still exist?

Usually because the “used in filters” box is no longer ticked on the brand record, or because the filter cache hasn’t been regenerated since that change.

### Does the cache need rebuilding after every new product?

After a one-off addition, the cache usually updates itself. After a bulk import, it’s safer to force a manual rebuild to make sure the whole catalogue is accounted for.

### The filter module may have been disabled by an update, how can I check?

Checking the module list in the back office, searching for the faceted search module, shows directly whether it’s active.

### Can I filter on a field that isn’t a standard attribute or feature?

Not with the native module. That requires specific development, extending the filter logic to a custom catalogue field.

### Do filters slow down category page rendering?

A properly built filter cache doesn’t slow the page down: that’s precisely its job, avoiding recalculating combinations on every visit. A missing or corrupted cache, on the other hand, can force costly calculations on every load.