When are page versions created?

1 Numbering of page versions

Page version numbers are constructed like [Major Version].[Minor Version]. The very first page version number is 0.1. Whenever a new unpublished version is created, the minor version number is increased (e.g. 0.2, 0.3, …).

When the page is published, a new major version is created. If the last unpublished version was 0.8, the published version will get the version number 1.0. After 3.27, the next published version would be 4.0 and so on.

2 Actions that will create a new page version

  • Creating a page. This will create the initial version 0.1
  • Manually triggering “save” for a page (from the menu or the assistent frame)
  • Publishing a page
  • Requesting, that a page is published (sending it to the queue)
  • Start editing a page, that was modified since the last version, but not saved or published by the last editor.

If a user modifies a page, without performing any of the above actions, the page will remain locked for this user, even if the browser window is closed. This lock is automatically lifted after a configurable time (default is 10 minutes), which will make this page editable by other users. If another (or the same) user starts editing the page again (after the left over lock was lifted in between), this is considered to be a new editing process, and therefore, a page version will be created to mark the state of the page at the beginning of this new edit process.

3 Actions that will not create a new page version

  • Automatic saving during editing with Aloha Editor, e.g. when the tagfill dialog is opened.
  • Creating new tags using Aloha Editor (although those tags will instantly be saved).
  • Modifying a tag’s content using the tagfill dialog.
  • Modifying object properties.

Generally speaking, as long as the page remains locked for the editor, no new page version is created. The only exception is cancelling the page from the page menu, when using Aloha Editor. Cancelling will raise the lock, but restore the last page version, not create a new one.

4 Cancelling a page

If a user cancels editing a page, the last page version will be restored. This is the version of the page, when the user gathered the editing lock of the page.

5 Versioned publishing

Gentics CMS will make sure that pages dependant of one another will only use published versions of contents for display. Eg. using a page ‘News Article’ in an overview contained in page ‘Recent News’ will tie those pages together by dependencies. When one editor changes the page ‘News Article’ (eg. the page title to ‘Very Important News Article’) whithout publishing the page (he might want to do additional changes) the ‘Recent News’ page will still use the old version of the page named ‘News Article’. As soon as ‘Very Important News Article’ is published the overview will be updated accordingly and use the new version.

Versioned publishing is default behaviour. In rare cases you might want to always refer to the most recent version of a page, even if it has not been published yet. See the example below.


// disable versioned publishing
$FEATURE["disable_versioned_publishing"] = true;