In the menu module I created a new menu.
I then added menu items that linked to URL aliases.
I then added some sub-menu items under the first set of items.
I enabled the custom menu block.
The menu shows up - however, clicking on menu items that have sub items does not explode / expand the menu. It stays collapsed.
The menu.module properly indicates that the item is collapsed in its default state - but the menu does not expand when clicked on.
Also - no breadcrumb information is displayed if you follow any links.
All links are to "page" nodes.
This is from a functioning properly updated CVS install.
andre
Comments
Comment #1
robertdouglass commentedYou have to use the node/123 url notation, not the alias. The alias would be nice, and this should be a feature request, but if you just want to get your menus working, use node/123
Comment #2
andremolnar commentedI suppose that I would file this under 'bug by design'. This is certainly unexpected behaviour - and shows an incompatibility between two core modules (custom urls and menu).
If there is further feedback indicating that this is indeed by design I will close this issue and generate a new feature request.
I'll also see if I can trace the code and generate a patch.
andre
Comment #3
andremolnar commentedI can see why this is the way it is.
And indeed this is best filed under a feature request.
Thanks for the help - the 'work around' - it works perfectly.
Can I help document this somewhere?
andre
Comment #4
andremolnar commentedThe new feature request can be found here:
http://drupal.org/node/11149
andre
Comment #5
(not verified) commentedI am having the same problem indicated by andre on that thread. But, in my case, I am using the node/123 url notation.
At the moment, I am migrating between versions so I am just doing some tests first. Drupal 4.5.0 is installed under /dru/ folder so the links end up like /dru/node/123. Could that be the problem?
Comment #6
jonbob commentedMore information, please, Anonymous? I just posted a patch for the originally cited issue, but haven't been able to verify your behavior.
Comment #7
jonbob commentedNo response in a month... we'll presume the patch fixed this unless someone can reproduce the problem and reopens the issue.