Apparent JavaScript error in UI
zwhalen - June 8, 2008 - 14:24
| Project: | Views |
| Version: | 6.x-2.0-beta3 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hello,
When attempting to add filters to a display, I get the following error in a Javascript alert:
"An Error Occurred."
The error console reports the following:
Warning: reference to undefined property E.cache[a][d]
Source File: http://devel.gameology.org/misc/jquery.js?9
Line: 13
This triggers after I select a field in the lower pane and click "add." This has also occurred when adding Arguments or Sort Criteria.
This first occurred in FireFox 3.0, but I reproduced in IE7.
#1
I'm getting this when I click on anything in 'basic settings' for an existing view.
Subscribing.
#2
As a further update, this problem is occurring across every browser I've tried it on, making Views basically unusable.
I've also discovered that after this error appears, my DHTML menus no longer respond. I tried disabling the DHTML Menu module, in case there was a conflict, but the error still appears.
#3
The DHTML menus no longer respond because the error you're seeing is a javascript crash. Unfortunately it's crashing inside jquery, which is compressed, so the error message is not very helpful to me. Meaning I can't debug this. :/
You can make Views usable by disabling javascript, I suppose. Hm. In fact, that can make an acceptable workaround, so I have committed that.
Most people are not experiencing this problem, but clearly a hand full are. I need to figure out what is different about your system that might be causing this, so giving as much information about your setup as possible would be good. Also, if you have separate dev environments, it might be helpful to try things out in other environments and see if you can get an installation working somewhere, and maybe start narrowing down things that happen.
Finally, it could be helpful to try firebug and see what the actual responses to the posts are. For the most part they should all be JSON responses; so if you see an actual web page in there, it could be a server issue.
There is some evidence that some particular situations might cause Views' AJAX code to call the wrong URLs, but I haven't narrowed down exactly what, yet.
#4
I'm using Firefox 2.0.0.14, on Windows 2000, running a local server with XAMPP version 1.6.3a.
Is this the output from Firebug you're after?
<pre>Views plugins build time: 76.137 ms</pre>{ "display": "\x3cdiv class=\"views-messages\"\x3e\x3cdiv
class=\"messages error\"\x3e\nwarning: Cannot modify header information - headers already sent by (output
started at D:\\xampp\\htdocs\\drupal-cvs-image\\sites\\all\\modules\\devel\\devel.module:1538) in D
:\\xampp\\htdocs\\drupal-cvs-image\\includes\\common.inc on line 141.\x3c/div\x3e\n\x3c/div\x3e\x3cform
action=\"/drupal-cvs-image/?q=admin/build/views/ajax/display/frontpage/default/use_pager\" accept-charset
=\"UTF-8\" method=\"post\" id=\"views-ui-edit-display-form\"\x3e\n\x3cdiv\x3e\x3cdiv class=\"form-radios
\"\x3e\x3cdiv class=\"form-item\" id=\"edit-use-pager-1-wrapper\"\x3e\n \x3clabel class=\"option\"\x3e
\x3cinput type=\"radio\" name=\"use_pager\" value=\"1\" checked=\"checked\" class=\"form-radio\" /
\x3e Full pager\x3c/label\x3e\n\x3c/div\x3e\n\x3cdiv class=\"form-item\" id=\"edit-use-pager-mini-wrapper
\"\x3e\n \x3clabel class=\"option\"\x3e\x3cinput type=\"radio\" name=\"use_pager\" value=\"mini\" class
=\"form-radio\" /\x3e Mini pager\x3c/label\x3e\n\x3c/div\x3e\n\x3cdiv class=\"form-item\" id=\"edit-use-pager-0-wrapper
\"\x3e\n \x3clabel class=\"option\"\x3e\x3cinput type=\"radio\" name=\"use_pager\" value=\"0\" class
=\"form-radio\" /\x3e No\x3c/label\x3e\n\x3c/div\x3e\n\x3c/div\x3e\x3cdiv class=\"form-item\" id=\"edit-pager-element-wrapper
\"\x3e\n \x3clabel for=\"edit-pager-element\"\x3ePager element: \x3c/label\x3e\n \x3cinput type=\"text
\" maxlength=\"128\" name=\"pager_element\" id=\"edit-pager-element\" size=\"60\" value=\"0\" class=
\"form-text\" /\x3e\n \x3cdiv class=\"description\"\x3eUnless you\'re experiencing problems with pagers
related to this view, you should leave this at 0. If using multiple pagers on one page you may need
to set this number to a higher value so as not to conflict within the ?page= array. Large values will
add a lot of commas to your URLs, so avoid if possible.\x3c/div\x3e\n\x3c/div\x3e\n\x3cdiv class=\"clear-block
\"\x3e\x3cdiv class=\"form-buttons\"\x3e\x3cinput type=\"submit\" name=\"op\" id=\"edit-submit\" value
=\"Update\" class=\"form-submit\" /\x3e\n\x3cinput type=\"submit\" name=\"op\" id=\"edit-cancel\" value
=\"Cancel\" class=\"form-submit\" /\x3e\n\x3c/div\x3e\x3c/div\x3e\x3cinput type=\"hidden\" name=\"form_build_id
\" id=\"form-3c90012e503bd78cacc8fe5eb201c581\" value=\"form-3c90012e503bd78cacc8fe5eb201c581\" /\x3e
\n\x3cinput type=\"hidden\" name=\"form_token\" id=\"edit-views-ui-edit-display-form-form-token\" value
=\"6718d578cff6e9c4bd738ce677e54b03\" /\x3e\n\x3cinput type=\"hidden\" name=\"form_id\" id=\"edit-views-ui-edit-display-form
\" value=\"views_ui_edit_display_form\" /\x3e\n\n\x3c/div\x3e\x3c/form\x3e\n", "title": "Defaults: Use
a pager for this view", "url": "http://localhost/drupal-cvs-image/?q=admin/build/views/ajax/display
/frontpage/default/use_pager", "js": null, "hilite": ".views-item-default-use-pager" }
#5
I'm not sure if that firebug data corresponds to what I'm getting (probably does), but I can add a little more info now. I've been using it with javascript turned off, as you suggested, and I was able to get a more specific error message.
This is all from memory since I've been away for a few days and I rearranged things on that Drupal install such that I can't test for this just yet, but if I remember correctly, the problem had to do with a particular date field that I was trying to select. My understanding is that this would indicate a problem in the Data API.
In other words, I think I selected a CCK Date field in the "Add Field" step, and (without JavaScript) encountered a fatal error in Date (or maybe it was Calendar?). I'm guessing that the same fatal error was being encountered earlier in the AJAX, but not being reported as such.
Sorry I can't be more specific. I've tried to re-create the error, but so far I've been unsuccessful, which I guess is a good thing. :)
#6
Yes, that is entirely possible; a bug in the date module could cause that to happen. Good info, thanks.
#7
I got this on a relatively clean D6 I want to use for working on image.module.
All I have on it is: admin_menu (doesn't work), advanced help, coder, devel, image, views.
#8
joachim: Your problem is devel.module -- if you update to views beta4 that should be fixed.
#9
Yup. Updated to beta4 and latest devel release, and it's working now!
#10
It sounds as though everything I can address here has now been addressed.
#11
Automatically closed -- issue fixed for two weeks with no activity.