Versioning And Rollback

Versioning can be turned on/off for any specific content type – so has to be turned on for the specific content type in question. Out of the box, all relevant content types have versioning turned on.

Editing a live content item creates an underlying DRAFT content item. When this is approved, the current live content item database record is archived. This archive is permanent by default, although many folks set a maintenance task to wipe archives older than a certain date. The limit is really a question of database size - these days that's pretty much as many as you like.

There is an option to archive associated media assets such as images and files. These are copied to a specific archive location outside of the web root.

Rollback is based on the record only. Most of the time this is all you need. However, if you have changed or deleted the associated content templates (display methods) the restore will show the current look and feel or only show a dump of the record in question respectively.

System wide attributes for content include createdby, lastupdatedby and owner fields. Plus there is an audit trail for all activities which you can report against.