How to fix common issues
This section describes the most common problems that customers report and how they can be resolved.
Filter is not visible on some category pages, while it remains visible on others
For example, you have discovered that the color filter is visible on some category pages and not visible on others.
This can happen because specific category's filter consist of a single option and filtering by this option does not reduce the number of the displayed results. Such options serve no purpose, so they can be hidden, and a filter with no other options disappears from the page.
This happens only when Hide Inactive Filter Options is set to Yes in Stores -> Configuration -> Layered navigation filters -> General Settings. If the setting is No, these options and filters are shown.
Hide Inactive Filter Options works for the Category filter starting from version 2.9.44, and for attributes with OR multiselect logic starting from version 2.10.8. On older versions, enabling the setting does not hide such options in these filters. Upgrade the extension to get this behavior.
The second reason for it can be the Categories visibility mode configuration in the Layered navigation tab of attribute edit menu, where you set the scope of categories where to show or hide this filter.
The Price filter shows a single price range option
Magento allows you to configure the price step setting on the category and system levels.
If the price filter shows a single range only for a specific category, navigate to that category settings by Catalog -> Categories, open the tab Display settings, and verify the field Layered navigation price step.
If all categories display a single price range, then you should check the system level price step settings.
- Go to Stores -> Configuration.
- Expand Catalog dropdown and click the Catalog link of menu.
- Navigate to the Layered navigation section and expand it. Verify and adjust the price settings if needed.
You can learn about price navigation configuration and its methods in official Adobe documentation.
Visiting a filter URL redirects to the same page with all filters cleared
This happens when the request applies more filter options than allowed by the Max applied filters setting (Stores -> Configuration -> Layered navigation filters -> SEO settings -> SEO configuration). Every selected option counts toward the limit, so two colors and one size count as three.
Increase or clear this setting if legitimate shoppers are being redirected. Filtering via AJAX on the page is never affected — only direct navigation to a filter URL that exceeds the limit is redirected.
A filter URL with query parameters redirects to another URL
When Enable SEO friendly URLs is set to Yes (Stores -> Configuration -> Filter SEO URLs), a URL with filters in query parameters, like /gear/bags.html?color=49, is permanently redirected (301) to the SEO-friendly URL of the same filters, like /gear/bags/black.html. This is expected: a filtered page keeps one address, and search engines move the ranking of the old URL to the new one.
If the redirect leads to the page without filters, the URL had filter values that do not exist in the store, so they were removed.
To keep an attribute in query parameters, set its Enable SEO URL option to Disabled in the SEO Filters tab of the attribute. Learn more in the redirect of filter URLs with query parameters section.
The gear icon in the Filters Manager does not respond
If nothing happens when you click the gear icon of an attribute in Content -> Layered Navigation -> Filters Manager, open the browser developer tools (Network tab) and reload the page. If the request for Mirasvit_LayeredNavigation/js/filter/utils.js (or utils.min.js when JS minification is enabled) returns a 403 error or a Cloudflare challenge page, the file is blocked by a firewall rule.
This happens when a Cloudflare WAF rule (or a similar firewall rule) blocks requests with the word filter in the URL path. The Filters Manager scripts are located in the js/filter/ folder, so the rule blocks them as well.
To fix it, change the firewall rule so that it does not apply to static files. For example, exclude:
- paths that start with
/static/; - paths that end with
.js.
After you change the rule, clear the browser cache and reload the Filters Manager page.