Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Wim,
I've been out of the HS loop for a good 2-3 months and have been getting my hands dirty again with the rc6 version.
This issue I brought up in June: #259903: When using "Save Term Lineage", term data not saved on node/edit.
This issue is still very much a problem. I've done some testing with rc6 and the point I mention in the last post or two of that thread is still happening.
I use PathAuto for this node type to create URLs as such:
city/[termpath-raw]/[field_city_name-raw]
when I use "save deepest term only", the URLs come out as:
city/united-states/texas/dallas-county/dallas
now I've switched to "save term lineage", they are coming out as:
city/united-states/dallas
this was happening with rc2 and is still happening with rc6. Any ideas what is causing this? If I can't get those URLs coming out correctly, I can't use "save lineage" at all which is a real shame.
Secondly, once I've altered the config for a vocabulary to "save lineage" from the previous "save only deepest term", when I go into a node, the terms have to be reset. I suppose that's normal. But I have about 700 nodes saved like that...am I going to have to manually go into each one and reset the taxonomy terms so that the lineage is saved? This of course is something that will only be an issue if I can get the first problem resolved, so that I can use "term lineage".
thanks as usual for a great module.
Comments
Comment #1
wim leersSorry for the slow reply. School is killing all my spare time.
Problem #1
I don't know why I didn't figure this out when you posted that other issue. But termpath couldn't work properly, because it doesn't know how to deal with save_lineage. See this post:
You should start using the newly provided
[save-lineage-termpath-raw]token and all your problems should go away thanks to that.Problem #2
That's a tough one indeed. There's an issue for that as a feature request, too. I guess that there is one thing I could do: iterate over all nodes of all content types with which the vocabulary is associated, get all parents for the first term found (when the dropbox is disabled) or all terms (when the dropbox is enabled) and then store these.
The problem is that this won't scale, but that's sort of acceptable, because you wouldn't change this after you've got 10,000 nodes. For 700 nodes it'll probably be fine.
Let me know if you still need this.
Comment #2
esllou commentedI will play around with rc7 and see if things are better now. One thing I didn't understand about the new token:
- The special [save-lineage-termpath] token only works if the vocabulary that
has save_lineage enabled, is the only vocabulary. Furthermore, it does work
with content_taxonomy fields, as long as you have the "Save option" set to
either "Tag" or "Both".
so if I have 5-6 vocabularies, this won't work? I only want "save lineage" and to use this [save-lineage-termpath-raw] token on one of them.
Comment #3
wim leersGood catch, I guess I forgot to update that bit of documentation.
That's been fixed in RC7. In RC7, there is the [save-linage-termpath:vid] token, where you can specify a vid to enforce the termpath of a specific vocabulary. Previously, it would pick the first one.
I'll update the documentation.
Comment #4
wim leersFixed! :)
Comment #5
wim leers