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.
Comment | File | Size | Author |
---|---|---|---|
#11 | 2355531-missing-exposed-input-warning.patch | 1.1 KB | roderik |
|
Comments
Comment #1
digibrill CreditAttribution: digibrill commentedSame here - subscribing
Comment #2
_grizly CreditAttribution: _grizly commentedI was getting this as well, my
hook_form_views_exposed_form_alter
function was removing empty filters from the form, so the url parameters weren't there for processing. To prevent the error I slightly patched the views handler (It doesn't appear to have broken any of my dozens of other views):views/handlers/views_handler_filter.inc line 1273
from:
to:
Initially it appeared as a "boost" issue, the sheer volume of "selective filters" in the view was making the urls too long for the filesystem to save a "boost" copy. And bots crawling my site was making it lag with the infinite variations in so many input filters.
How many &a=All&b=All&c=All's do you need before your "Clean Urls" become ugly again?
Comment #3
alansaviolobo CreditAttribution: alansaviolobo commentedI have a view with exposed filters.
when I visit the page for the first time, I get these warnings ( as the url does not have those params )
I dont have any custom code that touches the urls. not sure why this is happening. but the hack provided worked for me.
Comment #4
derekrezek CreditAttribution: derekrezek as a volunteer and commentedi am getting the following notice on the views edit page:
i have added a filter on a taxonomy term for which i have written a custom filter handler (by using _views_data_alter):
the custom handler looks like this:
here "categoryta" is a 3 level hierarchy.
The same code is working on production, but not in my local system.
I have tried flushing cache and trying different browsers and switching between different jquery_update versions.
Any help is appreciated.
Comment #5
derekrezek CreditAttribution: derekrezek as a volunteer and commentedi checked for the path entry for the class: views_handler_filter_lx_agnostic in registry table, and it was missing.
Comment #6
devad CreditAttribution: devad commentedI had similar errors in some of my views after I have updated views module to most recent version recently.
Re-saving views and their problematic exposed filters (you can recognize them by "undefined index" value) helped me to fix the issue.
Comment #7
rexfordnyrk CreditAttribution: rexfordnyrk as a volunteer commentedHello guys, I seem to have been having this same problem with the undefined index thingy after updating to the recent version. all my views worked perfectly without any such problems. but after update BOOMThe error!! anytime I try ti edit the that specific display the browser hangs executing ajax script, sometimes freezing the entire computer. but when I stop the script then the error shows and my computer comes back to normal.
Ok so I just went back to downgrade my views module to version 7.x-3.17 and it works
Comment #8
Dan_i_am CreditAttribution: Dan_i_am commentedThis problem started recently for me with 7.x-3.20. Re-saving the effected filter and the view didn't fix the issue in my case. The error message produced is
Notice: Undefined index: field_guide_status_value in views_handler_filter->store_exposed_input() (line 1395 of /var/www/html/stagegearank/sites/all/modules/views/handlers/views_handler_filter.inc).
The effected field is a multi-select box if that helps. Let me know if this should be created as a new issue.
Comment #9
martinhansen CreditAttribution: martinhansen at PeaceWorks Technology Solutions commentedSee other issues (in case this helps?):
https://www.drupal.org/project/views/issues/2961962
https://www.drupal.org/project/views/issues/2900405
Comment #10
sano CreditAttribution: sano as a volunteer commentedseeing this error in 7.x-3.20 patched with https://www.drupal.org/node/1183418 and https://www.drupal.org/project/views/issues/1877238
Comment #11
roderikI don't think this is related to any specific views version, and I'm not sure this is related to any of the referenced issues.
In my case, for whatever reason, one of the filter handlers was broken - and I suspect all responders from #4 until here had a similar issue. This may or may not be solved by re-saving the view; it depends on how broken the filter handler is, and why.
This issue cannot be solved by a patch. But we might help things by
It will then be up to you to actually check the view and see what's wrong.
Note this will not solve the issues encountered 5 years ago by
Comment #12
roderik