Closed (outdated)
Project:
Menu Trails
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
13 Oct 2010 at 09:27 UTC
Updated:
10 Aug 2025 at 00:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Eons commented+1
Comment #2
roam2345 commented+1
Comment #3
Andy B commented+1 subscribing
Comment #4
InvDeath commentedplease, do it
Comment #5
Andy B commentedChange title for better use in the dashboard.
Comment #6
peter törnstrand commented+1
Comment #7
johnalbinThose wanting a Drupal 7 solution for this underlying problem can check out http://drupal.org/project/menu_position
See #952384: Comparison with Menu Trails module for a comparison.
Comment #8
ivan zugec commentedAgree with JohnAlbin.
http://drupal.org/project/menu_position works perfectly on Drupal 7 thanks. :)
Comment #9
hoporr commentedThis module should still be ported to D7. The powerful feature is to tie a taxonomy term to a certain menu item.
Comment #10
lolandese commentedSubscribe
Comment #11
harryzhxu commented+1
Comment #12
sw3b commentedSubscribe
Comment #13
chriz001 commentedsubscribe
Comment #14
kris digital commented+1
Comment #15
kris digital commentedIf somebody only needs the core features of this module, like taxonomy and content-type dependent highlighting like me, I got it running for D7 without further testing and no warranties... It works for me, but it's only a prototype without organic group and token support etc. Settings are here Structure->Menue->The tab on top that says trails
Comment #16
Gessle commented+1
I have to test the prototype sometime!
Comment #17
xandeadx commented+1
Comment #18
momper commentedsubscribe
Comment #19
xandeadx commentedI chose http://drupal.org/project/menu_position + pathauto
Comment #20
fax8 commentedyeah, the menu_position + pathauto combo is pretty powerful.
Comment #21
rudiedirkx commentedyear2036's menutrails_d7_prototype.zip works perfectly! Thanks!
Comment #22
goldlilys commentedSubscribing
Comment #23
bowersox commented+1
Comment #24
Floop commentedsubscribing!
Comment #25
barbun commentedHello, guys!
I spent some time trying to port this module to D7. For my project it works great!
I also installed it to the clean D7 and then ran a quick test and it went good. So, i hope it could be useful for you.
I didn't have a possibility to check organic groups support, so i just commented this part of the module. Besides, i re-wrote taxonomy support and output theming.
Feel free to ask if anything strange occurs. I will be glad to share my knowledge and fix possible bugs, in spite that i'm newbie in Drupal.
Here goes the full module in a zip. Patch to be provided!)
Comment #26
Sylense commented+1. I tried the patch but I have OG installed and so I was given a fatal error
Comment #27
lonehorseend commentedsubscribing
Comment #28
corentin commentedsubscribing
Comment #29
jorisx commented+1
Comment #30
anybody+1
Comment #31
porg commentedDear maintainer: Could you please add some info like this to the project page:
Drupal 7: A compatible version of menutrails is currently developed (See: #940206: D7: Upgrade/migration path from Menu Trails to Menu Position module ) and as an alternative you can try the module menu_position , which is already compatible with Drupal 7.
Comment #32
sunCan someone post an in-depth analysis for what is actually missing or different in menu_position compared to what menutrails provides?
The intentions to maintain this module further are very limited, because it seems like plain and pure duplication of efforts at this point.
It would make a lot more sense to figure out what's preventing current users of menutrails from using menu_position currently, and possibly fix that, and ultimately write a migration path from menutrails to menu_position (in case that doesn't exist already).
Comment #33
oxyd commented+1
Comment #34
theresel commented+1 subscribing
Comment #35
Greg Varga commented+1 subscribing
Comment #36
sunPlease, can people just stop posting useless +1s here, read #32, and actually help moving this issue forward instead?
#32 was a direct response to #31. Adjusting status accordingly.
Thanks.
Comment #37
porg commented@sun: I already wrote all about I knew. "There is a similar module ready for D7, and this module may be ported to D7 too, and that info would be appreciated on its project page." That's it from me, hope I could clarify.
And please don't rant about those "unnecessary +1". This is simply because of Drupal.org 's lack of a good notification system, but this is soon solved #34496: [meta] Add Flag module to allow users to subscribe/unsubscribe without posting a comment. There may be a issue cleanup script of all "+1|(Ss)ubscibe(!)|…" comments, once it works fine!
Comment #38
basicmagic.net commentedsubscribe
Comment #39
r0b3rt commentedsubscribe
Comment #40
specky_rum commentedWhy would you want menutrails instead of menu_position?
For me I have a very simple requirement. I want menu items to stay highlighted as you work your way down the tree i.e. if my menu is structured like this:
a
|-1
..|-x
b
if I select x when that page renders I want a, 1 and x to all be highlighted. All I need for that are the li tags for each to have the active class assigned. As far as I can tell menutrails does exactly that out of the box. No config required. I have installed the version in #25 and (with a small fix) for simple node pages it works fine and exacty what I wanted. It doesn't work for my view pages but I'm not sure yet whether that's the module or Drupal core that's failing there.
Anyway... I also installed menu position which, in the description vaguely hints that it might do what I want but it seems with that you have to setup rules before anything happens at all and since all I want is across the board behaviour that seemed overkill.
I'd be happy to use menu position if someone can tell me how to achieve my goal.
Hope that helps.
Tom
btw. the slight fix to the version in #25 was as follows:
menutrails.module line 122:
was: ->fields(array('menu_name'))
should be: ->fields('menu_links', array('menu_name'))
Comment #41
johnalbin@djguvnor: You haven't explained your use case sufficiently. If you have a menu structured as you describe and a, 1, and x are all in the menu, then the highlighting you desire is done by core's menu module. You don't even need menutrails to achieve that.
Comment #42
mgifford@barbun Any thought about putting this up as a standard patch?
Also, running it with Coder is also a good practice.
Comment #43
rhawkins commented#25 plus the fix in #40 worked for me. There's also a print statement on line 128 that needs to be commented out.
The "patch" in #25 is actually a whole zip file of the module in d7 form. Settings are in Structure >> Menus >> Trails
Comment #44
Andrey Zakharov commentedLooks like project abandoned.
Will give a try http://drupal.org/project/power_menu though
Comment #44.0
sunUpdated issue summary.
Comment #45
sunThe recommended upgrade/migration path is Menu Position module.
I've clarified/rewritten the summary of this issue.
It looks like there is still no report about a use-case or functionality, which cannot be solved with Menu Position module.
If this remains to be the case, then the only remaining task is to ensure a working upgrade/migration path from menutrails to menu_position module.
Comment #46
Antti J. Salminen commentedHere's a little drush command I wrote that might help someone in migrating to Menu position. Works for creating equivalent taxonomy/content type rules:
https://gist.github.com/2719944
Comment #47
guyFawkes-2 commentedkrisdigital 's MenuTrails prototype works perfectly for me in combination with Nice Menus and Superfish Modules. Thatks!
Comment #48
Marko B commentedMain reason why menu position isn't useful for me is this
"This is particularly useful if you want a lot of nodes to appear as children of certain nodes / taxonomy term / views / referenced nodes / etc, but do not want to add them all to the menu. eg. hundreds of blog articles."
That is why I would use menu trail by path module, but Would like that menu poistion module also has this option a otherwise it's good.
Comment #49
sachandI would like to bring this module back to life , as i think this module will be helpful regardless of other alternatives available. Can i please get maintainership of this module ?
Comment #49.0
sachandUpdated issue summary.
Comment #50
avpadernoI am closing this issue, which was created for a project version compatible with a Drupal release no longer supported. Feel free to re-open the issue, if it is still relevant for a project version compatible with a supported Drupal release.