Path
exponential.earth / exponential / documentation / ez publish basics / content management in ez publish / content object versioning
Content object versioning
These documentation pages are no longer maintained. Please visit the new documentation site.
The actual content that is stored inside a content object can exist in one or more versions. Each time the content is modified, a new version is created. The old version remains untouched. This is how eZ publish keeps track of changes made by various users. The versioning system allows the users to revert/undo changes, etc. In order to prevent the database from being filled up by old/non-used versions, the administrator may set version limitations. It is possible to set the maximum number of versions on a content class basis.
Each version of a content object may belong to a different user. Only one version can be considered "published", this is called the current version. Using journalists and articles as an example, the following diagram presents a rough illustration of how the versioning system works.
The built-in versioning system is a handy tool that can be used to version control any kind of content (regardless of type/shape/structure/etc.). It basically provides a generic, out-of-the-box version-control framework.
Comments
Changing the number of versions
Helle Andersen
Friday 08 July 2005 9:34:41 am
This is an overall setting. It is not possible - unfortunately - to have different settings for specific classes, sections or sub trees.
# Define maximum versions can be managed. Use syntax
# VersionHistoryClass[class_id]=maximum_nr to specify value for particular
# classes. Otherwise, the value of DefaultVersionHistoryLimit will be used.
[VersionManagement]
DefaultVersionHistoryLimit=10
VersionHistoryClass[1]=5