Hello everyone,
After spending some time evaluating other CMS and Wiki options, I settled on CMSMS because of its feature set and short learning curve. One feature on my must have list was "content versioning". It seems that I will have to wait for 2.0 to see that feature.
For the present 1.2.2 release, might anyone happen to have an automated way of archiving content and selectively restoring it?
Thanks for all suggestions.
-drew
Content versioning - workaround?
Re: Content versioning - workaround?
If you mean expiration dates the news has this function that you can change to make it show again, remove exp. or change it or change the publish date with new exp. date...
If you mean to archive the whole site there is the archive module...
If you mean to archive the whole site there is the archive module...
Re: Content versioning - workaround?
Thanks for the reply Mark,
I'm looking for some way to automatically create an archive of an edited page. For example, a community website might edit the welcome page on a weekly basis. Having the ability to rollback to a previous version of the welcome page is what I refere to as content versioning.
Your news publish/expire date suggestion seems like a plausible option. Each versioned page would effectively be its own news page.
Another thought is to setup a blog for each page, where the latest entry becomes the current content. To revert back to a previous version, some way of changing the publish date would be needed.
I'm considering all options at this point. Eventually, it would be most useful if the content contributor could revert to previous page versions. For the short term, any workaround would require admin privileges/knowledge.
-drew
I'm looking for some way to automatically create an archive of an edited page. For example, a community website might edit the welcome page on a weekly basis. Having the ability to rollback to a previous version of the welcome page is what I refere to as content versioning.
Your news publish/expire date suggestion seems like a plausible option. Each versioned page would effectively be its own news page.
Another thought is to setup a blog for each page, where the latest entry becomes the current content. To revert back to a previous version, some way of changing the publish date would be needed.
I'm considering all options at this point. Eventually, it would be most useful if the content contributor could revert to previous page versions. For the short term, any workaround would require admin privileges/knowledge.
-drew
Re: Content versioning - workaround?
You may want to look at the Archive module as it is for rolloing back to previous versions of pages...