6 replies to this topic

[darren]

Is there a way to have some sort of version control within etomite? for example if I wanted to go back to content from 1 or 2 edits ago?

I'm feeling the need for this on a site, (someone else generating content) and other than creating new doc and unpublishing the current one I can't see how to do this.

I'd be great for the next release, anyway.

[Ralph]

Versioning is a concept that I have been kicking around for quite some time (almost 3 years) for inclusion in a major release... You won't see it in the current code base but it might sneak into the Cocoon release but I won't guarantee anything at this point... I'm sure that a backup could be hacked into the current code base but management for rollbacks would have to be done manually... I generally do Copy & Paste for any resources that I know I will be butchering in a major way and either save them within Etomite or as external text files on my local machine... This practice has saved my ass more than once or twice over the years...

[darren]

I'd need it more for content/page docs then resources, I usually make a copy of a template or snippet before I hack it up as well.

[Ralph]

darren, on Jan 8 2008, 03:44 PM, said:

I'd need it more for content/page docs then resources, I usually make a copy of a template or snippet before I hack it up as well.

I consider documents to be a type of resource and use the same Copy & Paste with them too... Granted, this wouldn't be convenient if you had several people maintaining content, but it sure beats running on caffeine and confidence... I simply toggle my WYSIWYG editor into HTML mode and grab the markup which I then save in a standard text editor file... I have discussed document versioning with several users over a period of time and we have concluded pretty much unanimously that such a feature would be beneficial...

[InfoNow]

I too am currently searching for a way to do version control for our Etomite system.

I think this is important for our various environments (development, staging, and production), and urge the feature for consideration in a future release.

Does anyone else have any ideas on how to implement this now without Etomite code support?

One idea our Etomite operator had was to export the database into flat text files, and check these into source control (Subversion). Source control should only store the text diffs, ideally. This is a bit ugly, but is there any better way to manage versions, or promotion of changes between the environments I mention without moving to a different CMS or waiting for an update release?

[Cris D.]

You could just use your document tree to stage documents at various points prior to publishing and showing in the menu. Eg in the repository have a draft folder, pre-production folder, a final authorisation folder and when checked, can simply be moved to the live folder. It's simple, not relly tracked and relies on good team communication, but a possability...

[darren]

Cris D., on Feb 22 2008, 06:46 AM, said:

You could just use your document tree to stage documents at various points prior to publishing and showing in the menu. Eg in the repository have a draft folder, pre-production folder, a final authorisation folder and when checked, can simply be moved to the live folder. It's simple, not relly tracked and relies on good team communication, but a possability...

I had thought of that process but it's more the idea of moving backward to content from several edits ago that is my 'need'. To hard for a non technical user to move a document to 'old document' folder everytime they want to change a page. This also requires them creating a new doc for every edit. its a thought though.