Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
exposed filters
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Jan 2011 at 16:22 UTC
Updated:
22 May 2013 at 07:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
jelle_soh, and using drupal 7.0
Comment #2
jelle_sChanging this to alpha1 version.
Error is still there.
Comment #3
dawehnerMove back to dev.
Comment #4
dawehnerThe error message:
This seems to be a problem of core:
Comment #5
ryan.armstrong commentedWhere in core is that?
Comment #6
dawehnerincludes/tabledrag.js.
Comment #7
ryan.armstrong commentedDereine: Thanks for pointing me to this duplicate issue. I'm still having the issue that when I turn AJAX off, the exposed filter disappears. Do you think this is related to this issue or a separate issue? I looked at my page code, and the filter isn't being hidden or display:none or anything, it just doesn't exist. I want to know if I should open a separate issue for that behavior, or if you think that this is all related to this toLowerCase bug.
Perhaps the issue is that something isn't being created correctly in views, so that when Drupal tries to go and create the table, information it needs is gone, thus the toLowerCase bit fails. I wonder if this is not a core issue, but still an issue with views, but part of the Table style rather then the filter system?
Comment #8
ryan.armstrong commentedOk, I was incorrect about it being part of the Table style. I changed the style to unformatted and I still get the same issues. I changed my theme to Bartik, just to double check, same result. I see the same thing happening in the views preview. With AJAX off, no exposed filters show up If I turn it on, I can then see the exposed filters but I get the above AJAX error.
Comment #9
minff commentedIt rather seems to be a problem of jquery.form.js, which is the only file in D7 that contains "a.tagName", or more exactly "a.tagName.toLowerCase" (i.e. error texts by FF and Chrome respectively).
Oh, and I see the same thing as described by Jelle_S: whenever I click on apply on an exposed filter of a view, the described error pops up. Ajax is never called (the error is output by ajax.js, row 256).
I'm using Drupal 7.0, Views 7.x-3.0-alpha1 and Ctools 7.x-1.0-alpha2.
Comment #10
ryan.armstrong commentedminff: Quick question, if you turn off AJAX, can you see the exposed form still? Does everything work just minus the AJAX?
Comment #11
minff commented@Ryan: Yes, everything works when I turn off Ajax.
Comment #12
duellj commentedThis is actually a bug in ajax_views.js. Here's what's happening:
Drupal.ajax expects the second parameter to be a DOM element. Views instead passes in a jQuery object containing the DOM element, so when Drupal.ajax tries to operate on that object (like retrieving the tagName) it fails. All that has to be done is pass in the actual DOM element instead of the jQuery object, which is what this patch does.
Comment #13
duellj commentedSetting to correct component
Comment #14
minff commentedWell, will you look at that, it works! Thanks.
Comment #15
dawehnerThanks.
Tested with a node and a user based view, with and without ajax.
This patch fixes the problem.
Commited to the 7.x branch.
Comment #17
thechanceg commentedI am using the views_load_more module, with the latest views 3.X dev from Jan-09-12.
I am getting this exact same error. And, as described above, if I turn off ajax for the view it works fine (albeit with a page refresh of course) I checked js/ajax_view.js and the patch from above was committed. Has anything changed since then that might cause this issue to pop up again?
I am also using drupal 7.0 if that makes a difference.
Export of the view, if that helps:
Comment #18
thechanceg commentedIt looks like Drupal 7.0 was the issue. I upgraded to 7.10 and the errors are gone.
Comment #19
j0rd commentedI'm getting this error when I attempt to "add no results behaviour" in views.