Closed (duplicate)
Project:
Drupal core
Version:
4.7.0
Component:
menu system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 May 2006 at 23:51 UTC
Updated:
10 Jan 2007 at 20:33 UTC
I am reposting this here as a bug from http://drupal.org/node/64120.
"I've created a new navigation block (called My Navigation) and have an Admin menu in it. I've got the Expand set to 'No', but the Admin menu items do not expand when I click the Admin menu, as it does on the standard Navigation Block. When I change the Expand to 'Yes' they are expanded (always).
I've searched and seen the problems with aliases and expanding. But the only way I know of getting the admin functions are using paths that look like 'admin/access'.
Does anyone know what the issue is or a good workaround?"
-----------------
I have the same problem and the workarounds suggested there do not work for me.
Thanks!
Comments
Comment #1
Jaza commentedThe problem is that the menu items for the administration pages already exist in a default Drupal install, so when you create new menu items for those pages, they are created as 'menu shortcuts'. This has nothing to do with URL aliasing, by the way (the menu system converts all aliases when it builds the menu tree) - whether you are using system paths or aliased paths , the issue is that you're creating two menu items for one page. A menu shortcut is not treated as the 'primary' menu item for a particular page, so things like breadcrumbs and navigation blocks are generated based only on the primary item.
For now, your best solution is to actually move the original 'admin' menu items from their default menu to your new custom menu.
However, I do think that this is a bug, and that the menu system should be fixed up to show the appropriate navigation context for shortcut menu items. I've just looked into this, and the solution that I can think of is quite complex - it would involve changing the menu system so that the
$menu['path index']variable is an array of possible menu items (with$menu['path index'][0]being the 'default' item), rather than just a single item. This would be a fairly major change to the menu system, and as such it will probably be quite a while before this happens.Comment #2
alewar commentedYou can go to the menu administration and in the original "Navigation Menu", first disable the item (for example settings), and then reset it.
After that the settings link will expand in the new menu and stop working in the original... not so optimal but resolved my problem.
Comment #3
Jaza commentedreverting title.
Comment #4
magico commentedThere are several issues against the menu system.
Marking this as duplicate of http://drupal.org/node/18351