Let me start with the message: I find this module simply brilliant, it helped me out so many times.
However during my projects, I also noticed that menutrails restricts some of the choices, which shouldn't be the case.

The following situation occurs:
You have a single content type called news.
You also have a views with an overview of these nodes.
You don't want the link of the overview page in the primary or secondary links.
You do want the trail of news content type to include the menu item of the overview page

To make this work, you can use a workaround:
1. Put an menu item in the primary-links to link to the overview page
2. Select the menu item in menu-trails
3. Make the menu item inactive

This will work as long as you don't change the settings in the back-end.
As soon as you change any settings, you will loose the breadcrumb and will have to repeat the process.

I found out that this restriction can be solved by allowing menutrails to be build up from several menu's
- This will open the option for people to use menu items from any menu they selected in the back-end.
- Allow people to create a dummy menu, to put menu items in they don't wanna show on front-end but do want in menu-trails.

I included a patch to help with this issue,

regards

TidalWave

CommentFileSizeAuthor
menutrails.patch2.17 KBTidalWave
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

TidalWave’s picture

Status: Active » Needs review
nedjo’s picture

Status: Needs review » Closed (duplicate)
nedjo’s picture

TidalWave’s picture

I dont agree that this topic is marked duplicate, since the other issue is about linking css classes based on the menu.
However I have posted my patch there in the hope somebody will review it.

bluesherpa’s picture

I installed the latest dev and ran this patch - no luck. It didn't solve the problem for me.

There is a primary menu item named Portfolio that has two sub-menu items called Websites and Articles. Like this:

Primary
- Home
- Portfolio
-- Websites
-- Articles

Articles points to portfolio/articles, which is supported by a view that lists content of type articles
Websites points to portfolio/websites, which is supported by a view that lists content of the type websites

If I point Portfolio to , the Websites menu item is highlighted when I view a node of type website.
If I point Portfolio to portfolio/websites, the Websites menu is NOT highlighted when I view a node of type website.

rkendall’s picture

@TidalWave - a quick test of your patch gave me errors.

Also, I would agree that #475684: Menutrails assignment fails if menu item is in any menu is a different issue, but what did you think was different about this issue to #630296: "Give first priority to the selected menu" doesn't work

TidalWave’s picture

@rkendall, I'll reroll the patch once I find some time for it. Now that I have a better understanding of how to provide patches.

Also I read the other issue, it still assumes that all items are in 1 menu. (ie. Primary Links). In practise I found several cases where you use multiple menu's. This provides better overview and with some tweaking allows you to restrict access to certain menu's (so clients can't mess it up). For example I use 'top menu', 'bottom menu' and 'primary links' to give items a certain place in the navigation. Now I can only select 1 of those 3 to create menu links with. If I would like to link a menu trail to an item in 'top menu' , it still doesn't work.

Now I know of alternatives, like using menu_blocks to chop up the menu into blocks and use that. But it was just as easy to make menu_trails use multiple menu's.

I hope to re-release the patch upcoming week.

Exploratus’s picture

sub.