Revisions and approval

Revisions

Every save of an item keeps a version of it: its text in every language, its address, its status, its dates and its place in the menu.

Seeing the history

Press History in the editor's header. Revision history lists every version, newest first, with who saved it and when.

Restoring a version

1. Press Restore on the version you want.
2. Confirm. The item returns to that version, and the version you had becomes part of the history too.

The restored version keeps its own status. Restoring a version that was published puts it back on the site, and restoring one that was a draft takes the item off. On a site that asks for approval, an editor's restore of a published version goes for review, the way a Publish does.

A version's web address is restored too. When another item now uses that address, the CMS names it, and you change one of them first.

Approval before publishing

An administrator can ask for every editor's work to be reviewed first, with Require editor changes to be approved before publishing on the Staff page.

Submitting

With approval on, an editor's Publish becomes Submit for review. The item waits, marked submitted, and every administrator gets an email, Submitted for review, with a link to it. A published item an editor changes leaves the site until it is approved.

Approving

1. Open the content list and pick the Submitted filter.
2. Read the item.
3. Press Approve to publish it, or Reject to send it back.

Approve publishes the item when its required fields are filled. The editor gets an email, Your submission was approved, with a link to the live item.

Reject asks for a reason. The item returns to draft, and the editor gets an email, Your submission was sent back, with your reason. The editor reads it at the top of the item, fixes it and submits again.

Administrators publish directly, with or without approval.