So I have the following structure:

Primary Links
--Item 1
----Item A
------Item i
------Item ii
------Item iii
----Item B
------Item i
------Item ii
------Item iii
----Item C
------Item i
------Item ii
------Item iii
--Item 2
----same as above
--Item 3
----same as above
--Item 4
----same as above
--Item 5
----same as above

I have a menu block that is showing level 2 based on where I currently am. So, if I'm in Item 1, I see everything under (and including) Item 1. If I am on Item B or Item C, I see the same menu, with the items under B or C (respectively) expanded. However, I cannot get Item A to expand by being on Item A. I have tested this for all level 2 menus on my system and it holds for every one of them. Item A will not expand when I am on it, whether I'm in Item 1, 2, 3, 4 etc.

Comments

JohnAlbin’s picture

Category: bug » support
Priority: Major » Normal

This is definitely not a bug in menu_block. As it just piggy-backs on core's menu building functions. You can confirm this by trying the same thing with the menu.module-provided "primary links" block; you should see the exact same behavior in that core block.

Are your "Item A"s special menu items? do they have paths that are duplicated in the same menu? i.e. does Item A have the exact same path as another menu item in the primary links menu? That's a known core issue.

beckyjohnson’s picture

I am having this problem and I am using special menu times.

Also using DHTML menu 6.x-3.5
and Special Menu Items module: 6.x-1.4

Update: I found if I changed the in special menu items to an li tag, it works again! That is the li tag is what the lolink class attaches to.
However, the .expanded class doesn't get attached and doesn't wrap around it's children properly.
Becky

JohnAlbin’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)