Closed (outdated)
Project:
Token
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Apr 2009 at 23:24 UTC
Updated:
24 Apr 2024 at 18:56 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
gregglesSame idea as the pathauto issue - thoughts?
Comment #2
exaboy commentedI have applied this patch and works when editing a node and when saving the new revision has the correct term used and path generated.
Comment #3
nonsieWorks great - cleaner solution than the original
Comment #4
gregglesCommitted to 6.x http://drupal.org/cvs?commit=199976 and 5.x http://drupal.org/cvs?commit=199978
Thanks, all!
Comment #6
eltrufa commentedThis patch is related to revisioning
module integration. Please see #423132: Incorrect retrival of node's taxonomy terms with revisions.
Thanks.
Leandro
Comment #7
dave reidIncorrect patch format.
Comment #8
bgilday commentedsubscribing
Comment #9
Sera commentedHi everyone,
this issue is still active for version 6.x-1.13.
I applied the patch in #1 and noticed, that if I choose only 1 term from my vocabulary, then the old term from the revision before is shown: e.g. my vocabulary consists of the terms "done", "open", "critical", and in r1 I choose "open" and in the current version its "done", then in the token the term is still "open" instead of "done".
Thus I added an if - clause. If I have only 1 term, then please take the tid that we already have in $original_term. This works for me. (Please note that I use php5.3)
If I have more than one terms, then my if clause is not choosen, but the module (incl. the patch) still doesnt work correctly. If there is more than one term selected within the node, the [term] is still one of the two terms... : e.g. choosing "open" and "done" (yes, that's illogical, nevertheless its an example) the [term] is "done". Thus for multiple terms the issue is still not fixed!
Nevertheless I hope that this addition still helps someone.
Best regards
Sera
Comment #10
marcoBauli commentedsubscribing, looking forward to test patch #6 in the correct format
Comment #11
bluegeek9 commented