Existing filters are not properly being removed when calculating min/max values

Hi,

thank you for you patch, it works great on version 7015.

Without it, the range slider doesn't keep the min and max values. That means, the selected min/max overrides the real min/max.

Hi,
thanks for this patch,
it also solves my problem that the original max/min range gets overwritten and you not could go back to the original range..

Great work

Yes thanks! Patch applied to latest dev worked for me.

I can also confirm that this patch works flawlessly with the dev version.

Thank you very much!

Hello!

drupal-7.36
search_api_ranges 7.x-1.x-dev (7.x-1.5+9-dev)
or
search_api_ranges 7.x-1.5

unfortunately the search_api_ranges-existing-filter-tag-2294807-1.patch and
search_api_ranges-text-input-fix-2392435-7.patch from https://www.drupal.org/node/2392435
did not help me. -of course I cheched that the patches applied correctly and changes were made.

With facet display widget - links, links with checkboces the filter works fine and deliver the correct values.
but when search api ranges come to play, the slider, min/max price fields does not work - after refresh the site, they still jump back to to default values and all items (products) are displayed.

What am I missing? How to solve please?

thanks
S.

Sorry commented on wrong issue......

Patch #1 works fine and it also solves issue 1989776 (original max/min range gets overwritten and you could ot go back to the original rang).

Works for me!!

#1 works great. Thank you!

Patch in #1 is working for me as well.

Just used this patch to fix the search_api_ranges issue for my site. Worked very well. Using search_api_ranges 7.x-1.x-dev this patch still is necessary, otherwise it is impossible to extend the search range back to wider values, once narrower values have been selected.

This patch is marked as committed but is not in the latest dev (2016-Mar-31). I'm not sure what to do in this case, so I've set the status back to "Needs Review."

Hmm interesting, I'll look into why the commit didn't apply the patch properly.

The default git branch wasn't set to 7.x-1.x like I would expect, which would explain why the change didn't show up. I've swapped the default branch. The next DEV build that Drupal.org generates should have this fix (and others) in it.

I tried to apply the patch in the OP, on the 7.x-1.5 version without success, so I made a new patch (with the same code) for the specified version in case anyone needs it.

I tried to apply the patch in the OP, on the 7.x-1.5 version without success, so I made a new patch (with the same code) for the specified version in case anyone needs it.

#20

#20