Incorrect finding of the parent term in the hierarchical taxonomy.
As result, for example, token "[node:vocab:1:termpath]" does not always work properly.

In my opinion, the reason for this is that the top-level term is determined by weight, although more correct to use the table "term_hierarchy".
Now this module use query:
"SELECT ... FROM ..{term_data} td ... ORDER BY ... td.weight ..."
and dont use table "term_hierarchy".

Comments

eresik’s picture

eresik commented

I wonder why nobody noticed before.

achton’s picture

achton
Location Denmark
commented

Subscribing.

lionux’s picture

lionux commented
Priority: Normal » Major

Upgraded the priority as this make the usage of this module unpredictable.

Tried to get two taxonomies with several level of hierarchy on my url, but one works, the other does not.
Not sure if this will break after an upgrade or not.

Alex Andrascu’s picture

Alex Andrascu commented

subscribing...got this aswell

achton’s picture

achton
Location Denmark
commented

This sounds similar to my issue in #1171324: Incorrect term selected for certain node revisions , please see if the approach in that patch can be appliede to this problem as well.