Skip to content

Version history and rollback

A restore brings back an old version's fields and layout, takes its status only if your role could make that move, and is itself saved as a new version.

Every save, publish and unpublish, and every workflow transition — submit, approve, reject — writes a new version snapshot: the row's fields and layout as they stood at that moment, numbered in sequence. Version history isn't something you maintain separately; it accumulates on its own every time content is edited or moves through the workflow.

What restoring a version does

Restoring writes a version's fields, layout and content-type custom fields back onto the live row. The layout goes back through the same validated write path an ordinary save uses, so if the module set has changed enough that the old layout no longer parses, the whole restore is rolled back rather than reviving a page nobody can open in the editor. Restoring isn't a rewind, either: it creates a new version recording the restore itself, so the state you just replaced is one step back in history, not erased.

Who can restore

Restoring needs editor or above. The status part of a restore follows the same ladder as any other status change, so a restore never moves a page further than your role's ordinary publish or unpublish could.

What each of the six roles can otherwise do, on content and across the rest of the admin, is Roles and the capability matrix. The queue a page's status normally travels through is Reviewing and approving submissions.