Add created/modified timestamps and authorstamps to all elements

[modxbot]

rethrash created Redmine issue ID 2027

The following elements should have created/modified timestamps and datestamps. This would provide a way to audit when the last changes occurred and by whom for tracking down issues and as a starting point for a simple versioning system. Would also mirror the content field. chunks
snippets
TVs
plugins
modules
manager users
web users

[opengeek]

opengeek submitted:

This will be addressed in Revolution 2.1.0-beta

[modxbot]

tracker_integration submitted:

A Pivotal Tracker story has been created for this Issue: http://www.pivotaltracker.com/story/show/3030025

[SebastienDaniel]

2.2.14-pl
Issue hasn't been addressed.

[exside]

yep, but I guess with Marks VersionX we have a quite good workaround =)...

[rtripault]

Is that still something we want into the core (considering some extras might achieve part of this feature already)?

Additionally, to track which user did change some the elements (according they are not static), one could use of the "manager action log"

[OptimusCrime]

All in favor of closing, VersionX works great for this.

[opengeek]

This is still valid and should be done in the core.

[exside]

would say so too =)

[adamwintle]

I don't think this is needed in the core, VersionX can handle it, plus you can look in the Manager Log to see whats been changed - perhaps a better Manager Log UI (wither better filters, etc)

However if this is implemented; would this record every modified timestamp or just the latest change?

Should this be bumped up to 2.6.0 milestone?

The problem with depending on the manager activity log is that anyone can clear it. There needs to be a way to save it to file before it will be dependable.

[adamwintle]

@sottwell That is a good point. Recently I was thinking that it could be useful if the Manager Log was a .log file on the filesystem instead of in the database. It could be in a JSON or YAML formate.

This way the Manager Log could be backed up to a secure and more permeant location (alongside other server logs) using a CRON job or other task runner.

Currently when I am running a content audit on a large site I rely on VersionX and the Manager Logs, but both of these can quite easily be manipulated.

If modified timestamp is added to all elements in the core it should be handled as a security feature with additional ACL/privileges integrations.