Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I merge 2 terms. Each term contains several nodes. Each of these nodes has some revisions. As a result of the merge is created a new term. But, a new tid is assigned for the first revision of each node, not for recent revision. New term has only a portion of nodes from previous terms.
In my opinion, new tid should be assigned to the latest revision of each node. Then, the problem with disappearing nodes doesn’t exists.
This patch is my proposal to solve the problem.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 579982.taxonomy_manager_merge.patch | 715 bytes | gdud |
Comments
Comment #1
gdud commentedThis patch is my proposal to solve the problem.
Comment #2
giorgio79 commentedsubs
Comment #3
mh86 commentedThe problem was, that the code was only relying on the nid column, but in drupal6 the vid and tid column form the primary key. From now on, all revisions are going to be updated (not only the latest one).