When one create's a new revision of the node with Content Taxonomy fields, the tags selected in previous revision aren't saved to database. Only the last version ID is being saved to the 'term_node' table. Maybe it is by design, and if it is, can we change it?

The Taxonomy module does save all revisions of a tag using the [vid] column in 'term_node' table. This makes it possible to track changes, for example, with the Diff module.

Comments

mh86’s picture

mh86 commented

there has been changes in beta 6 concerning the interaction with the taxonomy module, so maybe it's working now.
nevertheless, it should work the same as it does with other cck fields (any textfield, options etc.). when I create a new revision, I can see, that a new row with a new revision id is added to the database table and the old entries are still there. but when I use the show diff feature, now differences are shown... have you ever tried this with a different cck field? would be interesting if it's working

Taras Zavaliy’s picture

Taras Zavaliy commented
Status: Active » Fixed

Wow! It all works in beta 6 – thank's a lot.
Even the diff feature works. After I save the new revision of a node, I can see old revisions of tags saved into database, and the Diff module shows me the history of changes. This is great!

Taras Zavaliy’s picture

Taras Zavaliy commented

About that diff feature... Currently it works only with the Taxonomy terms. The Diff module requires an additional .inc file with the hook_diff() implementations for other modules. Currently, there are no implementations of hook_diff() for the Date fields and Content Taxonomy fields...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.