Closed (fixed)
Project:
Administration menu
Version:
6.x-3.0-alpha2
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Aug 2009 at 13:20 UTC
Updated:
30 Aug 2009 at 21:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
aacraig commentedYou should flush your cache. I had the same problem, flushed the cache, and the menu was back to normal.
Comment #2
Starminder commentedI lost the entire menu - flushing the cache has no effect.
Comment #3
asb commentedWhen I wrote "after running 'Flush all caches'" I tried to express that I've done exactly that ;)
Greetings, -asb
Comment #4
frank.dev commentedI have the same problem.
Comment #5
sunDid you run update.php ?
Comment #6
asb commented> Did you run update.php ?
Yupp, wenn updating through
drush update(this is running an updatedb automatically), and additionally as user #1.Greetings, -asb
Comment #7
sunok. I have no idea how to debug this, because I tested the upgrade path from 1.x to 3.0-alpha2 on a couple of sites and it all went smoothly there.
If you do not want to revert to a previous version, then a quick & dirty fix is to execute the following query:
WARNING: This query resets all administrative menu items defined by modules, so they are moved back into the administration menu.
Comment #8
asb commentedHi,
> I tested the upgrade path from 1.x to 3.0-alpha2 on a couple of sites and it all went smoothly there.
In my case I made an upgrade from 3.0-alpha1 to 3.0-alpha2, not from 1.x to 3.0-alpha2, so maybe that's the problematic part?
I just downgraded to 1.x (disabled, uninstalled & deleted 3.0-alpha2) which worked smoothly. Sorry for not being able to help testing 3.0-alpha2 a bit longer.
Greetings, -asb
Comment #9
Starminder commentedI went from A1 to A2 and experienced the problem and could not find a logical way out. Reverted back to A1, flushed cache, all is well - so at least going back works.
Comment #10
PRZ commentedSame problem. However, going back to A1 and flushing cache did not work to restore menus. I had run update.php for A2, so perhaps change to database won't allow me back to A1 state.
Comment #11
burningdog commentedI upgraded from alpha1 to alpha2, ran update.php and emptied my cache, and when going to /admin I get the message, "You do not have any administrative items." And indeed I don't. They're still in the admin_menu bar at the top of the page, but not on my admin page. If I go to admin/by-module I can access what I need to on the page.
Secondly, with the e-commerce module enabled the menu items in the menu bar look, well, confused. I've attached a screenshot (note: I'm logged in as user 1, but the bar isn't red, it's black -> it should be red). I'm thinking of reverting back to alpha1, but am happy to debug this further, if someone can point me in the right direction.
Comment #12
axel pressbutton commentedOddly enough, the only menu item i appear to have lost is Content management > Create content
There may well be more, but this one jumped out at me straight away
Comment #13
mieses commentedThe Administration menu is still missing after clearing all caches, running update.php, and "DELETE FROM menu_links WHERE router_path LIKE 'admin%';".
Adminstration Menu is still present in the list of menus at /admin/build/menu/list. But the Administration menu has been removed from /admin/build/menu-customize/navigation.
I updated from admin_menu-6.x-3.0-alpha1 to alpha2.
Comment #14
sun@Axel Pressbutton: "Create content" is a different issue: #502500: Re-add Create content
@all: I'll probably need Drupal + phpMyAdmin access to a few sites that were upgraded to alpha2 (without further customizations, such as the query noted in #7). If you want to help debug this, then please use my drupal.org contact form to send the necessary user credentials. Thanks.
Comment #15
axel pressbutton commentedThanks for that sun - totally missed that thread. Probably because I'd instantly associated to the update.
All sorted :)
Comment #16
mrfelton commentedsame problem for me. upgrading from A1 -> A2. I lost all entries from the administration menu, and accessing /admin results in a page stating 'You do not have any administrative items.'
I upgraded the module on two sites at the same time. One site was fine, the other broke. The one that broke had multiple site languages, if that makes any different.
Comment #17
snorkers commentedI upgraded from 3.0a1 to 3.0a2 and lost everything with the exception of the Druplicon (and system drop down), no of users online, logged in name (and user switch) and logout option. If the 'add local tasks' is checked then these would appear also.
Back to 1.5 then... :(
Comment #18
ratnesh aarohi commentedsame issue here:
upgraded from 6.x-3.0-alpha1 lost the menu and the warning - "You do not have any administrative items."
rolled back to 6.x-3.0-alpha1 - "phew" back to normal
Comment #19
adamo commentedI had the same problem ("You do not have any administrative items."). I had 1.5 on there before but I uninstalled it completely before installing the new version. Clearing cache and rebuilding menus didn't help.
update:
Same problem with latest dev snapshot.
3.0-alpha1 works great.
Also I noticed that in 3.0-alpha2 and above only the part of the menu that shows the logged in user is red and the rest is black. After rebuilding menus and flushing the cache with the latest dev, the admin menu was totally corrupt... Like, menu entries that should have been children ended up being siblings of their parents. :/
Comment #20
seanrUgh. This update just hosed one of my sites. Maybe you should pull the release until you figure it out so it doesn't keep affecting more people. One possible explanation: are all of you guys also using the admin module? I'm wondering if there's a conflict between the two now (never used to be).
Comment #21
seanrJust confirmed, the problem is the admin module. Disable it, and then flush the administration menu cache and your links come back. I'd love to know why admin is stepping on admin_menu - they should both be doing separate things.
Comment #22
adamo commentedI wasn't using the Admin module. I've never had it installed. There must be other modules 3.0-alpha2 conflicts with as well. I can post a list of the modules I have enabled if anyone is interested. If I have time I'll try to track down what module this is conflicting with on my site. For now I've gone back to 1.5.
Comment #23
burningdog commentedI'm not using the admin module either. The alpha2 release of admin_menu clears www.example.com/admin of all items on the page. I reverted to alpha1, cleared cache, and the admin items came back. Changed back to alpha2, cleared cache, and the admin items disappeared again. This is all that is displayed:
Comment #24
sun@seanr: Thanks! That's at least a starting point to investigate.
@Roger Saner: That's a different issue, namely: #511744: /admin page links are broken with latest development snapshot (which contains a patch that needs testing)
Comment #25
snorkers commentedJust to confirm that I have Admin module installed too, and alpha2 of admin_menu does not work correctly (ie, most links disappear, as described in this Issue). However 1.5 (which I am now running with) does work fine with Admin module
Comment #26
sunAdministration menu 1.x is completely different, and old, and ugly, and not comparable with 3.x. Please do not post that it works for you with 1.x, because that does not add any valuable information to this issue.
Comment #27
nigelcunningham commentedSubscribing. I updated from alpha 1 to alpha 2 as well, and am also seeing the issue.
Comment #28
fearlsgroove commentedHrm maybe this is bad timing, but MOVING the entire admin menu out of navigation doesn't seem like the right behaviour. If i want the administration menu under navigation disabled/hidden, I'll just do that. Why move the whole thing with no option, potentially disrupting any number of other features?
Comment #29
Starminder commentedAnother by-product of upgrading and reverting back to a1: I can't scroll down to the lower part of a menu if it is longer than the page itself. If you want it as a separate issue just let me know. Anyone else seeing this?
Comment #30
adamo commentedI'm with #28... I want the admin menu in both places.
Comment #31
sunThis is a major bug in Drupal core. See #550254: Menu links are sometimes not properly re-parented for more information. Also noted on the project page now.
I've committed the attached patch, which is a bad-ass workaround for this Drupal core bug. Took me 3 full days to find the cause in Drupal's menu system. And I'm sick of it. Totally sick of it.