| Project: | Tabs (jQuery UI tabs) |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I'm not sure if this is related to Vertical tabs, but I haven't got his problem before enabling this module.
If I have a page which uses vertical tabs (e.g. edit profile, edit node), sometimes Drupal won't load ANY Javascript. IE7 says that there is an error and I get this when I open the console:"Drupal.settings.tabs.speed error" is null or not an object
With Firefox the problem happens way less frequently, but using Firebug I get more info when it occurs.
Error: invalid object initializer
Source File: http://hlab.ee.tut.fi/piiri/user/register
Line: 63Error: Drupal.settings.tabs is undefined
Source File: http://hlab.ee.tut.fi/piiri/sites/hlab.ee.tut.fi.piiri/modules/tabs/tabs... 5Looking into the first error I get this
jQuery.extend(Drupal.settings, { "basePath": "/piiri/", "tabs": { "slide": false, "fade": true, "speed": "fast", "auto_height": false ...which continues for 20 lines or so. As you might notice, we have a multi-site installation of Drupal.
Looking briefly to vertical tabs code, I cannot see any value set for speed variable (which seems to be causing this problem), but I'm not a JS guru and don't know where the problem might hide.
Comments
#1
I'm not sure if the problem is the same but here is some discussion with similar problem
http://drupal.org/node/286171#comment-1202193
#2
Wrong module. This is a problem with the Tabs module.
#3
I'm getting this error with the latest version of Tabs 6.x-1.3 when used in conjunction with Popups 6.x-2.x-dev.
Firebug reports the following:
var fx = {duration: Drupal.settings.tabs.speed};I'm using Panel Tabs and on one of the Page's Panels, I have a link that uses Popups to display another Page in a AJAX Popup Window. When I click that link is when I get this error.
I'm guessing it has something to do with the order that the different scripts are loading, however, I'm not sure. I don't get this error when using Popups 6.x-1.3.
See the attached image for reference.
Link to a related issue posted in Popups' issues tracker.
#4
Last report appears to be a bug in popups.