Developer guide     >     Basics


The system records every change to the content or to the properties of a versioned object.

Object types that are subject to yeager's version control are PagesContent BlocksFiles and E-Mailings.
A given number of changes to an object is wrapped up into a "version". The number of versions for a given object is not limited.

In yeager there are two types of versions:

1. Un-approved versions - For internal use only.
2. Approved versions - For publication. Only approved versions can be published.
Users can roll-back to or preview previous un-approved or approved versions.
Every change that is made to a versioned object is made to the latest unapproved version. This version is called the "working copy" in yeager. When yeager users make changes to a versioned object, these changes always count to the "working copy".
Once approved, a version cannot be changed further. However, a previously approved version can be restored ("roll-back"). yeager then automatically creates a new version (the working copy), that corresponds exactly to the state of the approved version. Changes that are made to the object afterwards are part of the current "working copy".
Objects highlighted in green indicate they have yet un-approved changes.

Creating versions

There are two ways to wrap-up the current state of a working copy into a new version.

1. Approving the object automatically creates a new version of the object.
2. Using "Save snapshot as version" in an objects "Version"-tab creates a new version of the object.

Embedded Content Blocks

Embedded Content Blocks (unlike independent Content Blocks) are versioned along with the Page they are assigned to.


While File-objects are subject to versioning, they do not follow to the usual approval and publishing workflow: Files are automatically considered "approved and published" as soon as a change to a File property is submitted.
However, it is possible to roll-back to and preview previous versions of a File.
The "name in URL" property (available for Pages, Content Blocks and Files) is not under version control. Changes to this property are immediately applied without having to approve or publish that change. Accordingly, changes to this property are not documented in the version history of an object.