Revision Control

[lemkepf]

Hello all,
i work up this morning and had a brainstorming session about some of my projects... one of which might be a good idea for CMSMS.

Have we ever talked about "Revision Control" of the content/style pages? I've had many a time when i've wanted to "go back" to an old version without having to save it off every time. Personally i think this would be a very good idea as most Enterprise level CMS's have some kind of revision control.

Here are some suggestions if this ever makes it to the "future feature list".
1. Store this data in a different table to allow fast access to the "real" version.
2. Ability to show "differences" and compare between any of the versions. (ala viewsvn)
3. User, ip, datetime tracking of who made the change (ala wiki-style)
4. "view the site" basically load it into the "preview" window so someone can visualy see it.
5. Allow the same type of revision control of style sheets also.

I think it's a good idea, anyone else think it's good?

[cyberman]

Perhaps the archiver module can be tuned  ...

[Ryno]

I was thinking just the other day how important revision control is. I would love to see a module with this functionality get developed, or preferably, have this functionality built into the core.

[lemkepf]

I dont' see how a module would be able to access everything it would need... sure there is the archiver so you would manually backup ... but what about "i want to restore just this 1 page to last month". I think this would definitly set this CMS apart from the pack.

[Ted]

The archiver can do this.  It listens on the post-saving events in the module API and creates a new record for each one.