I have a question about configuring the module. I am using Drupal 7.10. I've gone through the following steps:

  1. Created a taxonomy and taxonomy menu
  2. Installed and enabled the Menu Block (7.x-2.2) and Taxonomy Menu Trails (7.x-1.3) modules
  3. Created a Menu Block with the taxonomy menu
  4. In the "Edit" page for the term reference field, select "Use this term reference to set active trail"
  5. Went to the "Taxonomy Menu Trails" tab within the content type and set the following:
  • Term references for setting active trail: (name of my taxonomy)
  • Term selection method: Deepest in Menu
  • Only if node doesn't have enabled menu item: unselected
  • Get term's path from Taxonomy Menu modules: selected
  • Additional path patterns for node detection: left blank

When I test the site, the taxonomy menu does not remain open when I open a node within that taxonomy. Did I miss any steps or do I misunderstand the purpose of this module? Any help you can provide is greatly appreciated.

Thank You


Dmitriy.trt’s picture

Thanks for detailed description of your problem! Module should do what you expect, I can't reproduce the problem on clean Drupal 7.10 install (Standard profile), Taxonomy Menu 7.x-1.1, Menu Block 7.x-2.2 and Taxonomy Menu Trails 7.x-1.3 (actually, latest code from git, but it is exactly the same as 7.x-1.3). See two screenshots:

Do menu items have paths taxonomy/term/[TID]? Did you created menu using Taxonomy Menu module or by hands? Did you changed settings of Menu Block? If yes, please describe changes (screenshot of block config will be enough).

I've just noticed that Taxonomy Menu Trails works with custom menus even without Menu Block, but this needs some investigation.
Sorry, custom menu still doesn't expand without Menu Block. It just keeps being expandable after Menu Block was disabled.

dgastudio’s picture

i have done the same, it doesnt work for me.

i can provide u an access to my website, if u can check please...

Dmitriy.trt’s picture

Yes, please send details through my contact form:

I'll try to investigate it tomorrow. Probably there is a conflict with other module or some special configuration which prevents module to work properly and we should document it.

Dmitriy.trt’s picture

Status: Postponed (maintainer needs more info) » Active

2 kervi: You have menu items with paths catalog/[tid], Taxonomy Menu Trails can't work with custom term paths yet. See #1268450: Add a hook to customize/override the term id to path mapping

Edit: Paths are actually taxonomy/term/[tid], catalog/[tid] is an alias. I'll continue investigation.

Dmitriy.trt’s picture

Status: Active » Postponed (maintainer needs more info)

2 Thelrin: Waiting for details.

Dmitriy.trt’s picture

Status: Active » Postponed (maintainer needs more info)

2 kervi: Actually, it works. I've disabled "Show as expanded" for top level term and when I'm on node page I can see:

  1. Catalog sub-menu is displayed in menu block
  2. Top level term menu is expanded

Link of second level term is not marked with "active" class, but it shouldn't. instead both top level and second level terms receive "active-trail" class. What also do you expect from module?

dgastudio’s picture

oh, great!

can u please give me an advice... now, the node is correctly ubicated under it's taxonomy term. but, that about breadcrumbs? how to set it to current menu path?


P.D. не заметил что у тебя в профиле стоит русский язык. Спасибо еще раз.

upd. solved problem with breadcrumbs: see: taxonomy_breadcrumb module

Thelrin’s picture

Thanks for such a quick response, sorry I couldn't get back to you sooner. My menu items have aliased paths, so I bet that's causing the problem.

Dmitriy.trt’s picture

Aliases don't affect active trail, because Drupal menu stores paths and not aliases (even if you enter alias on menu item edit form, it will try to get real path and save it instead of alias). If paths are taxonomy/term/[tid] then this is not the cause. It's easy to check: try to edit menu item, you'll see real path.

Summit’s picture


I tried the same configuration as set in this issue. I have may be one difference. I use panels node-page instead of normal node-page. Same configuration further as this issue.
I use Drupal 7.10. I added the patch to fix core where custom menu's where not expanded: http://drupal.org/node/942782. I use latest dev of Menu Block, Taxonomy Menu and Taxonomy menu trails.
What could be the problem please that on node-pages the taxonomy-menu/menu block blocks are not expanding to the active term? Also not on term-pages.

Without the menu block module, on term-pages, the active-trail is shown, and the block is nicely expanding, but on node pages it is not. With the menu block module and installation as explained at the top of this issue, I do not see any change, only that the active-trail is also not shown anymore on term-pages.

Could the core-patch have negative influences on this maybe? Thanks a lot in advance for going into this.

Greetings, Martijn

Dmitriy.trt’s picture

Hi Martijn,

Looks like with the core patch applied we don't need Menu Block to get expandable custom menu blocks. But I haven't tested Taxonomy Menu Trails for compatibility with this patch. I'll have free time on this weekend and I'll dig into this problem. Can I see the site with problem? You can use my contact form if don't want to publish it for everybody.

Thanks for your report.

Summit’s picture

Hi Dmitriy, I send you PM. Thanks a lot for going into this! Of course testresults we publish here for other users I think?
Greetings, Martijn

Dmitriy.trt’s picture

Thanks, Martijn. Sure, we'll publish results here after testing on this weekend.

Dmitriy.trt’s picture

After some testing I can say that changes introduced by #942782: Custom menus never receive an active trail breaks all Taxonomy Menu Trails versions from 7.x-1.x branch. I've created separate issue about it: #1413080: Drupal 7.12+ breaks Taxonomy Menu Trails

Dmitriy.trt’s picture

Do you still have problems with the latest TMT 7.x-2.0 version?

rimen’s picture

My problem is that menu_get_active_menu_names() function returns only standart system menus but not my custom menus, so
TMT doesn't work.

Drupal 7.12
TMT 7.2

Dmitriy.trt’s picture

Status: Postponed (maintainer needs more info) » Fixed

Marking this task as fixed. Feel free to re-open it if problem still exists.

Created separate issue about your problem:

eyal_barouk’s picture

Taxonomy Menu 7.x-1.2
Taxonomy Menu Trails 7.x-1.3
Drupal core 7.12

I have
1. a simple one level taxonomy dictionary set with Menu location = Main Menu.
2. term reference field, I have "Use this term reference to set active trail"
3. "Taxonomy Menu Trails" tab Term selection method = Deepest (?)
4. All Taxonomy Menu items expanded

But still, no active class is added to the taxonomy menu li

Dmitriy.trt’s picture

Links will never have class "active" on node page, but they should have class "active-trail" (which is not highlighted by default).

  • If your term link have "active-trail" just change your theme a bit to highlight links in active trail.
  • if "active-trail" class is not added please create a separate issue.

Also, please check this known problem: #1501968: Module doesn't work when custom menu is not in active menus list

eyal_barouk’s picture

Thank you for your reply.
To refine my question, my problem is that active-trail class is not added to the main menu li when displaying a node which has the menues' taxonomy item.
I am using drupal's main menu with a taxonomy menu. I am not sure if this is considered a custom menu, so not sure if http://drupal.org/node/1501968 helps my case.
I wil open a new issue for this then.

Dmitriy.trt’s picture

I've read again your previous message and realized that you're using wrong combination of Taxonomy Menu Trails and Drupal. Please, see compatibility table on the project page and upgrade to the module version compatible with your Drupal core (and don't forget to run update.php):

eyal_barouk’s picture

Great, it is working now... thank you so much for the help and contribution!

Status: Fixed » Closed (fixed)

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