When you're sorting by the Date Created in views, for some reason the view takes each date created for a particular node and outputs it again and again, even with Query Settings set to show no duplicates.

Unsure whether this is an issue with using Date Created as a sort criteria but I am working on a patch to resolve this now.

CommentFileSizeAuthor
#1 track_field_changes-multiple-records-2474247-1.patch2.81 KBMattWithoos

Comments

MattWithoos’s picture

MattWithoos commented
Status: Active » Needs review
StatusFileSize
new track_field_changes-multiple-records-2474247-1.patch2.81 KB

I've attached a patch that gives users the option to only store the latest record change for a particular node, rather than a history of all changes:

/admin/config/system/track_field_changes

Updated the track_field_changes.module database function and added a tickbox to track_field_changes.admin.inc

I've tested the patch and confirmed it is working as expected - will not store more than one record per node change if the tickbox is checked, otherwise if unchecked the module behaves normally as if it doesn't have the patch.

MattWithoos’s picture

MattWithoos commented
Status: Needs review » Closed (fixed)

This has been fixed in release 7.x-1.2.