I'm new to this module, and I'm having a strange problem where the submenu block will not show up at all. I've tried it on several themes to see if that was the problem, but still no luck. I'm testing it by using a parent menu NEWS, and I added three submenu links off of the parent. The 'MBS-News-1st' block shows up ok in my left column, and I have the 'MBS-2nd' block in the right column, but nothing ever shows in the MBS-2nd block when I click the NEWS link in the left one. I do get my news page to show though. Could it be that DHTML could be blocking it? I did disable it for my News menu.

CommentFileSizeAuthor
#2 menu.diff1.05 KBDekka
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

wxman’s picture

I need to amend what I just wrote.
I think I just must not be setting this up correctly. I've moved News the to a different parent menu called Content. It's there with a few others that all have sub menus. To keep using the news one as an example; the News page is from a view set to have a URL of /news. The sub pages off of the main news page are from taxonomy generated links like category/news/writer-news. I found that if I click one of these links from the main news page, the secondary menu does show with the sublinks in it. The submenu will not show when I'm in the main news page. It does the same thing with the other Views generated pages with sublinks. I hope I'm not sounding too random about this.

Dekka’s picture

FileSize
1.05 KB

I also stumbled over this bug or something like it.

For getting some required informations about the current item (received through menu_get_item()) the program matches $current_router_item['href'] against the database field menu_links.link_path. The Problem (in my case) is that in $current_router_item['href'] are no "+"s in the URL but they are in menu_links.link_path. The result is, that there is no match between the menu items and the subtree is not displayed.

I've written a small workaround. I am fairly new to drupal so i think this is not the final solution, but it works for me.

wxman’s picture

Hi Dekka

Thanks for the info, but I'm afraid it didn't help here. I'm going to try digging into the module a bit more to see if I can find where I'm going wrong. For all I know, it can't do what I'm trying to make it do.

miiimooo’s picture

I have noticed the 2nd level disappearing when I turn on block caching in the performance site config. Does turning off block cache fix the problem for you too?

wxman’s picture

That didn't help either.

Marko B’s picture

having the same problem with latest drupal 6.8 installed...

Marko B’s picture

Category: support » bug
Priority: Normal » Critical

i think i figured out problems. its only problem if u use VIEWS with this module. well it works fine with wiews unless you have passed argument in your view

so if u have view with page view set up like "myview" and then u add some menu item that says myview/myargument it doesnt work and drupal doesnt rendered it ok, i say drupal as it's menu.inc file problem in fact its this line in block module

$second_level_tree = menu_block_split_second_level_tree(menu_tree_page_data($menu_name), $parent);

where menu_tree_page_data is called then "below" array which tells which menu items are below this one, is not populated for menu items where u have "views link" with argument. So u should hardcore this views and then u wont have problem. Suggesting you set default variable for views and make its name myview/something and it should work then when u put myview/somthing in as menu item. Fixing this could be even core or views problem so i wont get into this, i just found out where it is :)

Marko B’s picture

ehh crayze stuff(overworking) forget everything i said, i found out what was the problem. It works in other parts but not here.

you have to assign to your paths in view(s) /% for argument(s) as views say to you but you maybe didnt listen as i didnt. It usually works if you dont add %, but here it goes into problems. so make your view paths like "myview/%" where % stands for argument and there you have solution i suppose :-)

robertgarrigos’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.