Although I found #1511148: Please make compatible with Search API Ranges which points to a duplicate issue on the Search Api Ranges module, I believe this is something different and somehow fall inside this module.

I am using search_api_ranges with the slider plugin. The slider plugin works slightly different to the links in most facet in a way that the filter is not combined with the AND/OR operator as you would expect with other filters. When you use the slider widget, only one filter is being used at all times, meaning that the same filter is replaced with its values instead of adding more filters.

If pretty paths is enabled, the filter is always appended, say the pretty is is price I get:

price/x/x/price/y/y

Hope it's clear, I will try to follow this up on the code, but it's all too new to me the search api and facet api, so any help or pointers will be appreciated.

Comments

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
CreditAttribution: hanoii commented
Title: Small incompatibilty with Search API Ranges » Improve compatibility with Search API Ranges
Category: Bug report » Support request
Related issues: +#1989776: Remember min/max values after apply facet

For what it worth, this can be fixed within search_api_ranges as it has its own handling when prettypath is enabled, I do wonder if there's a better way to do this, in a way prettypath is more aware of what another module does with the facet URL instead of having search_api_ranges have a special handling for this module?

I just submitted a patch to #1989776-23: Remember min/max values after apply facet that should fix it at least as a good workaround.