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.
It seems that views query parameters through the URL does not result in them being passed on to the query.
I have narrowed it down to the difference between $view->exposed_data
and $view->exposed_input
. As far as i can tell from the code, exposed_input is the parameters fetched from either form submission or URL, and exposed_data is only as it is through form submission.
exposed_data is used a couple of places, where it does not make sense to only handle data through form submission.
Comment | File | Size | Author |
---|---|---|---|
#7 | views_query_parameters-2841599-4.patch | 2.5 KB | mian3010 |
#3 | views_query_parameters-2841599-3.patch | 2.51 KB | mian3010 |
Comments
Comment #2
mian3010 CreditAttribution: mian3010 commentedAttached proposed solution.
Comment #3
mian3010 CreditAttribution: mian3010 commentedRookie mistake, sorry.
Comment #4
LendudeLets see what the testbot thinks.
Comment #7
mian3010 CreditAttribution: mian3010 commentedRerolled patch to apply to 8.3.x
Comment #8
Vinay15@mian3010, When you submit a patch, you need to mark the issue as "Needs review" in the issue metadata for the bot to test it.
Comment #13
arnested CreditAttribution: arnested at Reload commentedThis patch has some serious issues breaking other exposed views filters.
I came across this on the project where the patch was initial created to solve a problem. The problem it tries to fix stems from a misunderstanding of views sorting parameters and some not quite consistent fixes on top of that misunderstanding.
I'm closing this as "works as designed".