Closed (fixed)
Project:
Search API ranges
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2011 at 16:02 UTC
Updated:
18 Mar 2014 at 10:48 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedHi, I can't reproduce this, maybe it is related to your search setup. For example, I have a price and a discount slider, and they are correctly updated. Can you tell me more about your setup?
Comment #2
nbucknor commentedI played around with my search page a bit more and realized there are specific cases when it does not work. I'm using Search API Views page, along with 2 normal facets and 9 range facets.
The form ids for the slider forms span from "search-api-ranges-block-view-form" to "search-api-ranges-block-view-form--9"
If i change the the slide with the form id of "search-api-ranges-block-view-form--4", all sliders from 0 - 4 will have updated min/max values, while all the sliders between 5-9 will have their original min/max values. If I update slider 8, all sliders up to 8 will update, but slider 9 will not.
If you need more details, I can provide them.
Comment #3
Anonymous (not verified) commentedI can't reproduce this either. Remember, changing one slider influences the min/max values for each other slider, due the new search restriction. The slider values are not static, but dynamically adapt to the min/max values for the given filter environment.
I assume that was the issue? In that case, the behavior is normal.
Comment #4
nbucknor commentedSorry for the late response. No, that is not the issue. Let's say I have 10 filters, and I change filter number 5. In this case, filters 1 - 5 dynamically adapts their min/max values for the given environment (as desired). However min/max for filters 6 - 10 do not dynamically adapt to the given environment (which should be something like $78-$85), instead they retain the default min/max ( something like $0 - $100).
If I change filter 9, filters 1-9 dynamically adapt, but 10 does not, etc.
Comment #5
nbucknor commentedComment #6
Anonymous (not verified) commentedOk I understand now and have been able to reproduce it. Let's see how to solve this.
Comment #7
dicreat commentedsubscribe
Comment #8
merilainen commentedAny progress on this? I have the same issue with two sliders, using the second one will adjust the first one's range after page reload, but adjusting the first one doesn't affect the second one.
Comment #9
khiminrm commentedHi! I don't know if the bug in my case is related to this issue.
I have noticed a problem on my site with two sliders on one page.
One slider is based on price field, which has value for all entities and another slider is based on the field which can be empty. And when I use slider widget for second field, my first slider(price field) start showing wrong min value. When I use only one slider (for the same price field), it shows right min value. Id's of the forms are: "search-api-ranges-block-slider-view-form--2" for price slider and "search-api-ranges-block-slider-view-form" for the second slider.
Comment #10
khiminrm commentedTo #9. I think in my case the module works as design, but maybe if the second slider have default(not changed and submited) values it must not influence on min value of the first slider.
Comment #11
khiminrm commentedHere is the patch for version 1.4
It solves for me my problems with min ranges and the problem described in this issue.
Comment #12
Anonymous (not verified) commentedI made some minor improvements to #11, see attached.
It works well for me, when using 2 ranges. Can somone test if this works for 3, 4, 5 etc. ranges?
Comment #13
khiminrm commentedI've just tested the patch from #12 with 6 ranges. All seems fine.
Comment #14
khiminrm commentedI've tested the patch with last dev version.
Comment #15
khiminrm commentedComment #16
Anonymous (not verified) commentedThanks all,
committed to dev-x.
http://drupalcode.org/project/search_api_ranges.git/commit/309b649
Comment #18
windrainer commentedI don't get it, why not let the slider keep its original min and max value so the user can slide it back....