Active
Project:
Node changes
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Apr 2013 at 03:33 UTC
Updated:
7 Apr 2013 at 15:53 UTC
Jump to comment: Most recent file
Comments
Comment #1
dwwNo, this module supports a variety of field types, not just a few node properties. Not sure why you think otherwise -- was there some incorrect documentation somewhere? If so, please say where, so we can fix it.
Although similar, looks like Track Field Changes is trying to do something a bit different than we are. It might be worth merging the two, but a) nodechanges exists and works well for what D7 Drupal.org needs, b) I don't have time to review track_field_changes to see if it would help us.
I'm not going to "won't fix", but I'm not going to be able to work on this.
Cheers,
-Derek
Comment #2
nbchip commentedMy mistake, now it "works" on all fields. But I cant choose what fields to track, I can only choose additional 3 field properties.
Does it always track all the fields or am I missing something?
Track Field Changes has Views support and i was only suggesting merging cause of minimizing duplicate effort
Also i get bunch of - Warning: Invalid argument supplied for foreach() in field_load/formatter_view.
But I will file bug report when i investigate little more cause it now only works properly with properties and for other fields just prints field name.
Comment #3
dwwRight. In D7 certain aspects of a node are not actually "fields" in the pure Field API sense of the word. They're called "properties", and they're handled outside of the entire field system. For example, the node title (principally for performance reasons) and a few timestamps aren't actually fields, and the values are stored directly in the {node} table. nodechanges tracks all changes to fields automatically, and optionally also tells you about changes to some of these node properties, too.
Comment #4
dwwp.s. And yes, it always tracks all changes to all fields. The point of this module is really "show me everything that changed between two revisions" not "track changes to a specific field". But, perhaps it could be extended to let you decide which fields to track (or more accurately, to ignore)...
Cheers,
-Derek
Comment #5
nbchip commentedOk, Thank you very much.
It would be very useful to have ignore option.
So to make it clear, this module does not store changes in special table (and those no tracking) but it always adds comment with all fields that changed between last two edits.
thx.
Comment #6
dwwCorrect. The only storage about the changes is the field you attach to the comment bundle.
If you want the ignore option, please submit that as a separate feature request, ideally with a patch. ;)
Let's leave this issue just to discuss the possibility of merging with Track Field Changes...
Thanks,
-Derek