Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The range slider widget forces that the base slider processor is activated via isPropertyRequired() implementation, but it should be the range_slider clearly. Not only that this does not guarantuee that the really needed processor is enabled, this is actually forcing a misconfiguration resulting in SliderProcessor::postQuery() getting executed twice - one time from the range_slider processor itself and one time per directly calling the parent SliderProcessor class.
Comment | File | Size | Author |
---|---|---|---|
#2 | prevent_range_slider_double_processing.patch | 719 bytes | agoradesign |
Comments
Comment #2
agoradesign CreditAttribution: agoradesign commentedHere's the patch
Comment #3
borisson_Comment #4
borisson_Committed, thanks!
Comment #5
borisson_Comment #6
agoradesign CreditAttribution: agoradesign commentedWhere? Can't find it in the recent commit log!?
Comment #7
agoradesign CreditAttribution: agoradesign commentedNow I see... you were hiding it in that commit: http://cgit.drupalcode.org/facets/commit/?id=34d43b4
Comment #8
borisson_I'm afraid I messed up the commits, I committed a bunch of issues in one go and it got lumped in with http://cgit.drupalcode.org/facets/commit/?id=34d43b40b62a556e88e3eb2283e..., I can revert that patch and credit you again if you want.
Comment #9
agoradesign CreditAttribution: agoradesign commentedNo, forget it.. that's not that important.. Problem was that I was a little bit confused, as on updating the module, applying the patch failed, but I couldn't find the commit among the recent ones at first sight