Secondary Menu Block doesn't show for Page Views / Calendar / Blog
| Project: | Menu block |
| Version: | 6.x-2.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I'm using 2 Menu Blocks to show the first two levels of my Primary Menu. The 1st level has a link to 'Community' which has sublinks for 'Calendar' 'Blogs' 'About Us'. Since the 'About Us' is just a page node view the Menu Block shows fine, I have 2 rows of menus, one which shows the first level and one which shows the second level. However, when the user clicks 'Blogs' in the second menu which links to www.mysite.com/blog the second menu block disappears and it only shows the first level block. Same goes for Calendar and any Clean URL Page Views (for instance I have a Page View for Coaches which shows all Personnel content type of taxonomy Coach).
How can I get this second level menu block to show when I click a direct item on that menu which doesn't use 'node/#' anything that isn't in the node/ path doesn't seem to show.

#1
I noticed that if I create menu items to pages via the Views module that the 2nd level menu stays active but when I manually create a menu item that points to the exact same page the 2nd level menu disappears.
How can I put a link to Blogs and Forums on a second level menu and have the 2nd level menu stay active?
#2
#3
I've got the same problem, don't know how to fix it.
subscribing
#4
I've the same issue with a view page with argument.
At first look it seems to happen because when menu_block prune the menu, the entry for the page is not marked has being in the active trail. Following comment #4 in #235352: Primary links menu not following view page. I've found that adding a disabled menu entry to the view page without argument does solve the issue for me.
#5
I've got the same problem with showing image gallery without "node/".
#6
I added an argument element in the view path ("path/to/view/%" instead of "path/to/view") and it solves the issue for me.
#7
Wow seems to work now..thanks..