Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I upgraded to 6.x-3.0 alpha2 (02-August-2009) and lost the "By module" link under "Site configuration".
Running cron and flushing caches (Admin. menu cache) are not resolving the problem - only going back to alpha1 solved it for me.
Shows how important each little link is - especially this one - "By module".
Comments
Comment #1
skyredwangI confirm that modules, views.... disappeared
Comment #2
tryitonce commentedI guess the answer is that it was missed out when the module was compiled.
To activate this - in theory -
..../admin/build/menu-customize/admin_menu/add
Path: admin/by-module
Menu link title: By module
Save ->> this should take you to - ..../admin/build/menu-customize/admin_menu
Now you need to locate it and move it to the place you like - I actually moved it to Site building - because my Site configuration list is already too long.
So, let's see if it will stay there or be knocked over by the next flush = ;-)
Well, that was the theory. In my case this trick backfired - it seems that along the way Administration Menu - 6.x-3.0 alpha2 disappeared completely and kicked around my navigation menu to loose the Administration heading there.
So - back to 6.x-3.0 alpha1 - and all works again.
The only way to learn - try and error
Comment #3
sunThanks for taking the time to report this issue.
However, marking as duplicate of #511744: /admin page links are broken with latest development snapshot. Please search for existing issues before submitting a new one.
You can follow up on that issue to track its status instead. If any information from this issue is missing in the other issue, please make sure you provide it over there.
Comment #4
tryitonce commentedI would like to disagree on this point sun.
For the less experienced user following the path of not getting into development Drupal throws up the advice to check "availabe updates" and doing the "right" thing they will apply the new module. When this throws up problems they will look for the problem with the module or upgrade under the release, here 6.x-3.0 alpha2.
If we now refer a new user back to the development level it will send the wrong message - imho. I think it is much better if we can find the issues under the heading of the release where they occur.
With this little thread a less experienced user will at least have a confirmation it is not their fault and they will find a quick solution without spending hours trying to get into the deep end.
By the way this problem - #511744: /admin page links are broken with latest development snapshot - is not listed in the log or the documentation of 6.x-3.0 alpha2. Of course I looked at it after installation.
I totally appreciate all the fantastic work that goes into all the Drupal modules and are still amazed and thrilled to be able to find all I need essentially here. I would grumble about the rather limited documentation for lots of things - but it just shows how under-rated the skill of good documentation writing is. So the forums are a great way to get around it.
When I heard about Drupal I thought it is a no-no (some years back under D4) with a lot of conflicting threads and blogs.
When I started under D6 I gave it one shot -hence tryitonce-. I was lucky. The credit crunch gave me lots off time - otherwise I would probably not write this.
So, let us be a bit generous and help new, less experienced and users like me trying to find their way around without getting too deep into the development game to have issues duplicated where they would be looking for it.
Comment #5
sunI'm not entirely sure what you were trying to say with that follow-up.
#511744: /admin page links are broken with latest development snapshot is of course neither documented in the handbooks, nor in README.txt/CHANGELOG.txt, because it is a bug that exists in a (alpha) release of this module. Bug reports need to be unique to have a chance to get resolved, and you can follow up on that issue if you want to track its status. If there would be multiple bug reports for the very same bug, essential information for replicating and potentially fixing the bug would be scattered across multiple documents. So it is essential to the development and contribution process that one topic lives in one issue only.
Additionally, if you are a user who is not familiar with common development workflows, then I think you should not use alpha/beta/rc releases from any software - not limited to Drupal and Drupal modules. The common development workflow and release versioning is almost everywhere the same: An alpha/beta/rc release is new software containing new code that needs public testing and feedback from users - using common development workflows, i.e. reporting and elaborating on found issues and testing provided patches, to make the new code more stable and reliable. This applies to Drupal, Drupal modules, browsers (such as Firefox and others), and in general, to all open source software.
In this specific case, you are trying to use an alpha release of Administration menu 3.x. If you do not want to participate in the development process, then you are much better off with reverting to Administration menu 1.x, because that major version's code has been around for some time and is known to work.
Comment #6
tryitonce commentedSun, thanks - I take your point.
It seems that once you get into using an alpha release Drupal will flagging up the next alpha release in yellow as well. If I had stuck to 6.x-1.5 this would probably not have happened - sorry - always learning.
Maybe my note is a sign that Drupal is getting better and better allowing more people to use it with less hassle and hurdles.
We can happily close it here - thanks - great module - nothing is better then to keep it simple - just couldn't do without it.