I am currently encountering usability issues.
The entries in my taxonomy menu point to a term view that has two page displays.

The first display takes one argument, the name of the term:
The second display takes 2 arguments, firstly the name of the term and secondly the name of a node to show:

This way, I can have an overview page for the term on the first display, and a node-related view on the second display.

The problem is that, since I specify my destination path to be "mysite.com/vocabulary/%TERMNAME", the menu trail will not stay active in case I add another argument (mysite.com/vocabulary/%TERMNAME/%NODENAME).

Taxonomy menu trails could solve the problem, however, at the moment the path to the term view is hard coded and only allows the path to be "node/%nid". It would be a really nice feature to be able to specify a custom path to the term or even multiple if possible. This might solve the active menu trail problem with term views once and for all :)



Dmitriy.trt’s picture

Title: Custom paths to taxonomy terms » Custom paths to nodes
Assigned: Unassigned » Dmitriy.trt

We've discussed this by e-mail and you need custom path to nodes not terms. This will be the next feature for 6.x and 7.x branches.

Dmitriy.trt’s picture

Version: 6.x-1.2 » 6.x-1.x-dev
Status: Active » Needs review

Implementation was committed to 6.x-1.x branch and will be available in next 6.x-1.x-dev release. Please, test it and report about any problems here.

Dmitriy.trt’s picture

Implemented it for 7.x-1.x also (added custom paths migration from 6.x-1.x too). It is inside current developlent version. Please test it, because I'm planning to finally make a stable release for both branches on the next weekend.

Dmitriy.trt’s picture

Version: 6.x-1.x-dev » 6.x-1.3
Status: Needs review » Fixed

Feature implemented in 6.x-1.3 and 7.x-1.2.

Status: Fixed » Closed (fixed)

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