Revisions

Page revisions are page-scoped editorial safety snapshots.

They are designed for recovering the content and structure of one page without treating that task as a full backup or a site transfer.

Shared Slot revisions are separate site-scoped editorial safety snapshots for reusable Shared Slot content.

Both revision types can also carry compact audit metadata alongside the snapshot itself:

• actor user reference when a real admin user is known
• source such as admin, console, project_import, system, or restore
• event such as page_created, page_updated, workflow_changed, block_created, block_updated, block_deleted, block_reordered, slot_changed, or revision_restored

Older revisions may not have this metadata. The admin UI renders those rows as Not recorded instead of guessing.

Revision snapshots include:

• page core fields
• page translations
• page slots
• page block tree
• block translation rows
• media ID references

For page translations, the snapshot includes locale-aware SEO override fields as part of the editorial translation state. Restoring a page revision restores those page SEO values alongside localized name, slug, and path data.

Revisions are created automatically when these areas change:

• page fields and default translation
• workflow status
• page translation records
• slot structure
• block creation, updates, deletion, and ordering

When possible, the revision entry also records who triggered the change and what kind of workflow produced it.

Restore works in place on the current page.

When a revision is restored:

1. a fresh pre-restore safety revision is created first
2. the selected revision snapshot is applied to the current page
3. a new post-restore revision entry is recorded and linked to the source revision

This keeps both the previous live state and the restored state in revision history.

Shared Slot revisions are intentionally separate from page revisions.

• They are site-scoped and attached to one Shared Slot.
• They capture Shared Slot metadata plus the reusable Shared Slot block tree, including nested structure, translation rows, and media references.
• They do not capture unrelated editorial pages that reference the Shared Slot.
• They do not store page slot assignments as part of the Shared Slot revision snapshot.
• They carry the same compact actor, source, and event metadata pattern used by page revisions when the caller can provide it.

Restore works in place on the current Shared Slot.

When a Shared Slot revision is restored:

1. a fresh pre-restore safety revision is created first
2. the selected Shared Slot snapshot is applied to the current Shared Slot
3. a new post-restore revision entry is recorded and linked to the source revision
4. the Shared Slot id stays the same and existing page_slots.shared_slot_id references remain intact

Because Shared Slots are reusable references, restoring one can affect every page that currently uses that Shared Slot.

• super_admin: can view and restore revisions
• site_admin: can view and restore revisions within assigned sites
• editor: can view revisions within assigned sites, but cannot restore

The same access pattern applies to Shared Slot revisions.

• page-scoped editorial recovery
• focused on one page's content and structure
• Shared Slot revisions are separate and focused on one reusable Shared Slot's metadata and block tree

• environment-level recovery
• restores the current database and uploads from a backup archive

• site portability between installs
• used to move one site's content as a package

These tools are intentionally separate and should not be treated as replacements for one another.