Closed (won't fix)
Project:
Drupal core
Version:
5.x-dev
Component:
menu system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 May 2006 at 14:17 UTC
Updated:
24 Jun 2011 at 19:01 UTC
Menu links in 4.7.1 do not expand.
I've created some menus, one parent along with a few children. When clicking the parent, it does not display the children. Yet works with all default relationships drupal has by default. Also, I can see the children under the parent.
Currently I have this menu:
Tools (menu)
Saws (menu item / parent)
-Jig saw (menus item / child of saws)
Clicking on the parent does not expand the links.
Comments
Comment #1
stevenpatzIs this still an issue?
Comment #2
rewted commentedThough I'm currently running 4.7.3 and can't fully test on my production site, the issue seems to still be present.
Comment #3
pwolanin commentedI've seen this sort of problem when there are multiple aliases for one or more of the menu items. Is this true in your case?
Comment #4
rewted commentedYes... all menu links are aliased, none of which are the same though.
Comment #5
marc.bauwhats happen to this issue? i have this, too and need a fix.
Comment #6
pwolanin commentedLet me clarify my comment above- I think the problem actually occured when mutiple menu items (not aliases) link to the same page. However, I'm not seeing it now using on 4.7.3. Have you tried making a test site and upgrading to 4.7.3?
Comment #7
marc.baui am using 4.7.3... this occour on a test and a live site with aliases. without aliases it do not occour - BUT this don't help anything. i don't like to use such bad URLs like node/12 and node/13. URLs must be self speeking... and a tree structure must looks like
example
example/level1-a
example/level1-b
example/level1-b/level2-a
example/level1-b/level2-b
and so on...
Comment #8
millo commentedJust to verify that I've got the same problem here. I've followed Lisa's instructions on how to create multilingual menus (http://drupal.org/node/65182#comment-125220). This all works fine. Now the only issue is the menus not expanding when using url aliases.
Comment #9
AjK commentedIt may well be that there are more underlying problems with the menuing system as a whole.
Example:- http://drupal.org/node/72674
Comment #10
marc.bauhi
i found a solution yesterday, this problem is therefor solvable... but it's a bug. You only need to change your workflow and a minor thing in the menu items.
exampleand a menu item in the navigationnode/12345node/12345is dynamically overwritten by drupal on page load with the URL aliasexamplenode/12345and do NOT useexample!if you have older and existing menu items and you are trying to simply change the priior created url alias in the menus from "example" to
node/12345this may not work! i have deleted all my menu items an recreated them automaticaly from drupal, by recreating every existing menu item in the edit node pages.Comment #11
magico commentedConfirmed. Still happening.
Anyway, it was said that a new menu system is under development...
Comment #12
chris.gr commentedThe solution by marc.bau does not work for me, unfortunately.
I have two menu blocks. They differ in the way that in one menu block, I have more submenu items. One menu block is called when the user is logged in, the other when not.
Menu Block A
Menu Item CC
Submenu Item DD
Menu Block B
Menu Item CC
Submenu Item DD
Menu Item EE
Menu Item FF
I created a content page with a url alias (activities/cds) and let Drupal generating the Menu Item CC in the first block (with path node/42). The same for Submenu Item DD (with path node/44).
The menu worked fine, expanding worked as expected.
But then I created those two items in the 2nd menu block. (With node/42 and node/44 as urls). Here, the submenu does never expand.
I'd really appreciate it to get some hints!
Comment #13
pasqualleThis version is not supported. Reopen or create a new issue if the problem exists in any recent version (version equal or above Drupal 5)
Comment #14
magico commentedPlease pay attention.
I've confirmed this happens in Drupal 5.
Comment #15
sy278 commentedand still happening in drupal 7
Comment #16
dpearcefl commentedConsidering the lack of activity on this issue and that Drupal v5 is no longer supported by fixes or patches, I am going to close this ticket. If this issue still exists and you want to continue to ask for technical support from the community, please reopen and update this ticket.