I have observed that in cases where a node has a published revision with a vid lower than the max. revision for that node, the wrong term might be returned. This happens because Taxonomy Token does not take into account which revision is actually published for the node, but assumes the one with the highest vid is the right one, which is not always true.

This patch takes into account the vid of the node in question and retrieves only the term for that revision.

CommentFileSizeAuthor
#2 bad_terms-1171324-2.patch957 bytesachton
taxonomy_token-node_revision.patch937 bytesachton

Comments

Anonymous’s picture

Anonymous (not verified) commented

Thanks for this patch.
I had to remove an extra comma at the end $node->nid
But it works fine

achton’s picture

achton
Location Denmark
commented
StatusFileSize
new bad_terms-1171324-2.patch957 bytes

Here's a corrected patch.