Categories
- {Parent} Term 1
--- {Child} Term 2 = Taxonomy list of nodes
------ Node 1 - contains multiple terms
------ Node 2
------ Etc.
--- {Child} Term 3
- {Parent} Term 4
--- {Child} Term 5
------ Node 1 - contains multiple terms
------ Node 2
------ Etc.
--- {Child} Term 6

{Parent} menus are collapsed in menu settings.

nodes contain multiple taxonomies (tags) including {Parent} Term 1, {Child} Term 2, {Parent} Term 4, {Child} Term 5

When clicking to Node 1 under {Parent} Term 4, {Parent} Term 1 is always expanded. It seems to select the first parent term to expand no matter how navigating there.

How would I keep the parent term expanded, and the child term as "current/active" depending on the term the user clicked to display the node?

Comments

hles’s picture

Project: Taxonomy Menu » Taxonomy Menu Trails
Version: 7.x-2.0-alpha2 » 7.x-2.x-dev

I'm curious how you got that menu from 2.x version because it does not handle list of nodes within a menu item. Anyway, it looks like Taxonomy Menu Trails maintainer may be better qualified to answer this question. Changing of project.

dmitriy.trt’s picture

The question is a bit non-clear. I suppose the nodes are not in the menu, but they are listed on the term page.

You can't keep specific subtree opened on the node page depending on the list of terms visited previously without huge workarounds like parsing referrer to get the list of terms. And this could be a really complicated and sometimes impossible task because of custom paths support for the menu items.

But we could provide a better way for this, because it's not the first time people asking about this feature. What if there will be a way to get the list of terms on the node page from configurable $_GET parameter and select active one from these terms only? Some kind of terms filter.

To use that feature you should be able to change the term listing page and add query argument with the list of current terms to each node link. I mean, links on the term page should be converted from: http://example.com/node/1 to http://example.com/node/1?term=10 or to http://example.com/node/1?term[]=10. And the node page will react to this argument and select active term from the terms filtered by the argument.

Would it be helpful?

crutch’s picture

Okay I will try that suggestion, thank you Dmitriy.

---- Below is just trying to clarify original question, but will work on this week, thank you

Apologies, because it is a bit confusing

Just experimental at this point trying to decide whether to use the menu system as secondary navigation or a taxonomy menu (preferred) as secondary navigation for certain sections of many content nodes (in essence: Education Nodes)

- The Education Nodes are in the menu system (added automatically), primarily for breadcrumbs but this should not effect anything with taxonomy navigation.
- Multiple terms related to the education are selected by the "content contributor" when publishing a node
- Those terms are also displayed on the node and are clickable.
- I'm testing a taxonomy menu in the left margin with taxonomy menu trails.
- The menu sample above is a taxonomy menu.

Usability test
- I visit/find an Education Node by searching the site with term "DNA"
- This node has multiple assigned terms
- The taxonomy menu is then displayed in left margin
- I'm interested in other "DNA" Education Nodes so I click the term "DNA" {Child Term 5} in the taxonomy menu that displays a list of Education Nodes with the DNA taxonomy
--- The expansion of terms is okay here, also the breadcrumb is replaced with a taxonomy breadcrumb and is okay
- I then click to specific node for which I'm interested
- On node display, the taxonomy menu and breadcrumb use the first Parent and First Term assigned to that Node which is not term "DNA" causing confusion to the user.

I think this is the natural Drupal Core reaction and not necessarily TMT.

dmitriy.trt’s picture

Project: Taxonomy Menu Trails » Drupal core
Version: 7.x-2.x-dev » 7.x-dev
Component: Miscellaneous » menu system

This issue is actually about Drupal core and its menu system behavior.

dcam’s picture

Issue summary: View changes
Status: Active » Closed (fixed)

I'm closing old support issues for which an answer was provided and accepted.