Closed (fixed)
Project:
Admin
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
24 Mar 2011 at 17:24 UTC
Updated:
20 Sep 2012 at 13:58 UTC
Jump to comment: Most recent file
I have Admin module (7.x-2.0-beta3) installed and it has been functioning normally. Today I wanted to update JQuery from 1.4 to 1.5 and installed the JQuery Update module to do so. After the install the Administration menu in Admin no longer works. Disabling the Jquery Update module returned the menu listings.
I will be providing a screenshot of what is happening as well as posting an errors that show up the debugger.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | jquery.drilldown.js_.diff | 1.3 KB | praestigiare |
| #7 | jquery.drilldown.js_.diff | 1.44 KB | dat.pham |
Comments
Comment #1
mfer commented@fregan The issue is in the admin module. The JavaScript syntax it is using is not compatible with jQuery 1.5.1.
Admin module maintainers, can you please update your jQuery syntax to work with both jQuery 1.4 and 1.5?
The error I get in firebug is:
The path in the href is always the current path.
Comment #2
fregan commentedThanks mfer. I posted over there also, just wanted to post here as well.
Comment #3
OnkelTem commentedSubscribing
Comment #4
drupalicious commentedsubscribing
Comment #5
lightstring commentedSubscribing
Comment #6
dat.pham commentedHi
You can manual fix with flowing step by step:
1) Open file: /includes/jquery.drilldown.js
2) Change line 125
Form
TO
=> Add " before & after settings.activePath
3) Repeat step 2 with line 127, 148.
Dat
Regards
Comment #7
dat.pham commentedHere is patch.
Comment #8
mfer commentedThis is definitely a bug. The quotes are mandatory according to the jQuery documentation. Previously, I don't think this was enforced.
Comment #9
mail@victorquinn.com commentedSubscribing
Comment #10
pifantastic commentedI want to confirm that @dat.pham's patch works for me in 6.x-2.0
And @mfer is right, attribute selectors must be either a CSS identifier (http://www.w3.org/TR/CSS21/syndata.html#value-def-identifier) or a CSS string. In our case we're matching on a URL that is not a valid CSS identifier, so we need the quotes.
Comment #11
skwashd commentedThanks for the patch.
Committed to both the 7.x-2.x and 6.x-2.x branches.
Comment #13
just_one_fix commentedi dont have this file /includes/jquery.drilldown.js. - drupal 7.2
Comment #14
atlea commentedI see there is a lot of commits going into 7.x-2 since beta3. Perhaps you could add a dev tag to 7.x-2.x? :)
Comment #15
praestigiare commentedJust re-rolled the patch to make it compatible with drush make.
Comment #16
aidanlis commentedCan we get this in 6.x-2.x as well?
Comment #17
aidanlis commentedAh, patch has already been applied in 6.x-2.x branch.
Comment #18
mrP commentedFixed in 7.x-2.x-dev, not in 7.x-2.0-beta3. See #1378082: Fails to list menus for administration but shows when disabling jQuery Update 7.x-2.2
Comment #19
mgiffordJust posting a possibly related issue - #1360288: Panels 7.x-3.x-dev not compatible with jQuery Update 7.x-2.2 (jQuery 1.5.2 and jQuery UI 1.8.11)
I had the issue with the Admin Menu and other basic parts of Drupal's interface. Autocomplete, Module Filter, accordions were also giving me trouble with 7.x-2.2 enabled.
Only error I could see was:
TypeError: 'undefined' is not an object (evaluating 'settings.facetapi.facets')Comment #20
myselfhimself commentedHello,
it seems that current 7.x-2.0-beta3 tar.gz release does not have that
href="'+settings.activePath+'"quotes fixed. 7.x-2.x-dev has it. Is it not possible to port the double quotes patch to 7.x-2.0-beta3 ?Thanks in advance !
Comment #21
skwashd commentedThis fix will be included in the next 7.x-2.x release of admin.
Comment #23
shaneforsythe commentedIs there any update to this?
The last release of the -dev version was almost 1 year ago. The proposed solution/patch have been available since Nov, 2011 ... is there some blocking issue that is preventing this one patch to being applied and a new -dev version being released?
Comment #24
shark commentedJust reporting that the patch (#7/#15) works on Drupal 6.
Note that as of September 2012, there has not been a new stable release of Admin 6.x-2.x so other users with this problem will need to use the dev version or apply the patch to their stable module (which presumably is fine as the next stable release should include the corrected code).