Filter Revolution: setup and help

Upload and install the Filter Revolution ZIP in Modules > Module Manager. Click Configure, or open Filter Revolution in the back office.

Select the intended shop. Open Dashboard and use Rebuild Index for an existing or imported catalog. Wait for a healthy completed result. If the index exists but facet aggregates are missing, use Rebuild Facet Aggregates.

Open Filter Templates and review the installed templates and Default filter templates assignments. A matching template and a usable index are required for the filtering workflow. Test one category before changing the whole catalog.

Open Filter Revolution > Settings > Configuration > Display.

Product save/delete hooks maintain affected index rows. Other catalog changes invalidate filter caches and listing revisions. Rebuild after imports that bypass normal hooks, or when the dashboard reports unhealthy index/aggregate state.

The module registers the shared scheduled task Listing cache catalogue check (listing_digest). Its default interval is 300 seconds and proof grace is 1800 seconds. It uses a shared MPR cron runner when that package is available. Ensure that runner executes cron-context tasks; this module does not ship a separate cron.php command. The digest timing keys are internal configuration, not fields in the standard form.

Open Configuration > SEO.

Ordinary generated combinations are not automatic indexable landing pages. The module applies noindex to generated filter pages and listing-control variants. Canonicals depend on the listing surface and central SEO integration. With central SEO authority, ordinary category filter page one uses the base category canonical; standalone filtered pages can retain a filtered self-canonical. Do not assume that every filtered URL always canonicalizes to the unfiltered category.

Curated indexable pages need an eligible active SEO record and localized content for the exact shop and language. Check the actual returned canonical and robots values on your shop.

Current crawl protection integrates generated filter rules and curated exceptions with MPR SEO robots management. The old Disallow filter paths in robots.txt opt-in switch is not present in this form. If Configuration reports that robots are custom, missing or enforcement is off, enable robots management in MPR SEO and run Filter Revolution's integrity repair. Inspect the published robots file afterwards. Do not paste the old blanket example rules over curated exceptions.

When the module reports missing slugs, use Allocate missing slugs in Configuration. You need edit permission and a selected shop context. The action allocates missing identities while preserving existing URLs.

Example formats, using the vocabulary generated by your shop:

Stored facets: color:red/size:m
Public path: color/red/size/m
Ranges: price/10-50 or weight/1-5
Compact unique value: 120-x-120-cm

Copy a real working combination from your storefront when creating an SEO page; names and localized slugs vary by catalog.

Open Filter Templates. Set Template Name, Page Type, optional Default Exclusions, the Filters and Assign to Categories.

Supported listing contexts include category, search, manufacturer, supplier, best-sales, new-products and prices-drop. Select a default template for each listing type in Default filter templates. Category-specific assignments take priority over the fallback. Empty category assignment means a broad category template; confirm the selected default rather than assuming any unassigned template will win.

Drag entries from Available Filters to Active Filters (drag to reorder). You can use attribute groups, features, price, weight, manufacturer, supplier, condition, stock, category and on-sale filters. Attributes and features come from your native catalog.

For each active filter, choose its widget, Columns and Visibility dependency. New filters start with checkbox, one column and always-visible dependency mode; price and weight default to sliders, and condition defaults to radio. Allowed widget choices depend on type. Attribute and feature groups can support checkbox, radio, dropdown, numeric slider, color or image widgets. Price and weight use sliders; stock and on-sale use checkboxes.

Dependency modes can keep a filter always visible or require any/all rules. For example:

[{"filter_type":"feature","id_value":166,"values":[565]}]

Replace the IDs with the relevant feature and values. Default Exclusions stores rules that hide marked products until their marker filter is selected. Start with no exclusions or dependencies, then verify each rule on the storefront.

Additional filter defaults are position 0, product counts on, show limit 0 and collapsed off. These values are not all available as separate controls in the template builder.

Use the image manager from the templates area for attribute values and feature values. Upload WebP, PNG, JPG/JPEG or GIF. Non-WebP files are converted to WebP, requiring server GD WebP support.

Current storage is shop-specific under the PrestaShop image directory:

img/mprfilterrevolution/shops/{id_shop}/attributes/{id_attribute}.webp
img/mprfilterrevolution/shops/{id_shop}/feature_values/{id_feature_value}.webp

The renderer can prefer a template-specific {id_template}_{id_value}.webp variant over the generic value file. Use the admin upload workflow rather than putting new images in the old module-local img/attributes directory. The image storage directory and its access-policy file must be writable during setup.

Open SEO Pages and add one record for a deliberately chosen combination.

Save and open the exact page in each language. Fill distinct useful metadata or H1 content in each language you intend to index. An empty translated row does not inherit indexability merely because another language is complete. Eligible variants can use their own canonical and appear through the gSitemapAppendUrls integration; sitemap output also depends on route and crawl eligibility.

Use Configuration > Theme styles for detected colors, borders, radius, font and transition tokens. The module also exposes its Loading overlay value, default rgba(255, 255, 255, 0.7). Theme CSS can use .mpr-filter-container, .mpr-filter-group, .mpr-filter-group--active, .mpr-filter-active-tag, .mpr-filter-swatch, .mpr-filter-image-swatch and .mpr-seo-content-top.

1. Open a category with its matching template and confirm useful facets appear.
2. Select and remove filters. Confirm products, counts, active tags, pagination and URL update together.
3. Reload or share the resulting URL and confirm the same selection.
4. Test price ranges, stock modes and products-per-page controls.
5. Test the mobile drawer/offcanvas below the configured breakpoint.
6. For SEO pages, inspect returned metadata, canonical and robots and check the sitemap and published crawl rules.

The module uses PrestaShop product search provider integration and listing AJAX updates. It can also supply filter sections to Search Revolution through actionMprSearchRevolutionRenderSections. A custom listing or theme still needs to support the corresponding integration.

If filters do not appear, check the active shop, default and category template assignments, catalog index and whether the theme renders the filter area. A facet with fewer than two useful values can be hidden by the default visibility settings.

If results or counts are stale after an import, rebuild the index and aggregates. If a URL is rejected or an SEO page is not eligible, check existing slugs, exact combination identity, localized metadata and the robots status. Use Settings > Integrity for installation and infrastructure checks.

If controls update the URL without updating results, inspect JavaScript errors and the listing AJAX response. Recheck custom container IDs and mobile shell overrides. If a setting appears to do nothing, distinguish the legacy SEO/URL fields from the listing rules described above.

Back up templates, SEO pages and swatch media before uninstalling through Module Manager. Uninstall removes module configuration and menu entries, removes shop swatch media, reconciles the module's robots rules and runs table cleanup. Recheck the theme's filtering provider afterwards.

Requires PrestaShop 1.7.6 or later and PHP 7.1 or later.