Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
node system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Apr 2006 at 15:21 UTC
Updated:
14 Oct 2016 at 11:03 UTC
Jump to comment: Most recent
Comments
Comment #1
killes@www.drop.org commentedYes this is known. It wasn't considered important at the time of creating the revisions patch. Feel free to provide a patch after 4.7 is released.
Comment #2
pukku commentedFair enough.
Although, at this point it works better for me this way, so perhaps I shouldn't be too anxious to get this fixed.
Comment #3
LAsan commentedAny insights about this issue?
Moving to 7.x dev.
Comment #4
LarsKramer commentedI think the correct way for tracking changes to a term would be to implement a revision system for taxonomy. Or perhaps to separate the revision system from node.module and make it availabe for all entities.
Related issue: http://drupal.org/node/540118
Comment #5
jibranFor D7 you can use https://drupal.org/project/taxonomy_revision module. But I think it is little late for D8 in the cycle to add this kind of functionality. Perhaps 8.1.
Comment #6
berdirThe original issue was about revision support for node/term assignments, which already works since 7.x as it relies on the field system. *Not* revisions for terms.
Supporting that sounds like a separate issue, feel free to open one. Reverting and marking as fixed.
Comment #8
Anonymous (not verified) commentedHas the solution of taxonomy revision come for Drupal 8?