I have terms structure, for example:

russia (0 level, parend)
--moscow (1 level, child)

when editing a node, for hierarchical field I choose russia, then moscow, and save the changes.

both terms - links.
that all works as designed.

if I press moscow - i see all nodes with the term moscow.
If I press russia - no one node found, but I created a hierarchical structure russia-->moscow.

for a given entity, set the possibility to choose at least 2 terms.

as it should be? or is it bug?
I need not inly see hierarchical structure, but i need to set both, parent and child terms for nodes.

thank U for your help.

Comments

fomenkoandrey created an issue. See original summary.

stBorchert’s picture

Status: Active » Closed (works as designed)

This is intended, as SHS does not save the term lineage. There have been multiple discussions about this in the issue queue.
Using views and a filter like "Taxonomy term (with depth)" allows you to display terms associated to a child term (i.e. "moscow") when clicking on "russia".

fomenkoandrey’s picture

it's not really something.
I do not need to show the child terms through views.
I need to have both terms through the node: the parent and child.
I need to have possibility to show all nodes with "moscow" or all nodes with "rusia".
I planned to use the mod to ensure that it was possible to choose the child by the parent when adding/editing a node.

diogo_plta’s picture

"SHS will never save the lineage as its not designed to do"
I hadn´t imagined this module whitout this function. For me it is designed for this. Why save only the last item?
Can you explain? I think that a lot of people want this function.
Please, enable this possible, we already have a patch sugestion https://www.drupal.org/project/shs/issues/2943357

chike’s picture

I will have to uninstall this module now because it is not saving the lineage, it is only saving the last child, I thought it was a bug but now having read here I see it is the way it is designed to work. It is not right in my opinion, if I wanted to use only the child then why would I make a tree.

I am building a news publishing site and I have a term Business and I have child terms Capital Market and Commodity Market, I forced selecting deepest level so when I create a node I will be forced to drill down to Capital Market. So when I saved and I looked at term page for Capital Market I found the node but when I looked at term page for Business I did not find the node. This means that the Business parent term was not tagged.

So what's the need then, I rather list all terms on one level.

But really what other use case is this module for; tagging only the last hierarchy.