Template and custom-design recovery

Documentation / Saving, recovery, and troubleshooting

First identify which layer owns the damaged content. A template-bound page combines template-controlled areas with page-specific editable content. A custom page stores source-based body or header design. A shared shell supplies site-wide regions. Recovering the wrong layer can leave the original problem unchanged or reverse unrelated work.

Template-bound pages

Check whether the problem is in a locked template area or the page's editable slots. Inspect the owning template before restoring the page alone. Template changes can affect several pages, so review representative dependent pages after any recovery.

Templates and template-bound pages are excluded from normal editor cloud autosave. Do not assume Resume saved edits will recover a lost template edit. Preserve the current saved state and ask an administrator to inspect available template backups or snapshots when needed.

Custom page design

A custom body does not retain a synchronized native copy. To return to managed editing, inspect an earlier native page revision and explicitly restore suitable content and mode. Retain the real header, current identity, route, and language as appropriate.

CMS Custom design scope and video controls use their own saved drafts. Review Open saved draft, confirm I reviewed this saved draft, and publish the reviewed scope, or choose Discard scope draft. Discard leaves the live page unchanged. These controls are separate from assistant direct page updates.

Shared-shell recovery

Under Settings > Design > Shell > Revision history, Restore into a draft creates a new reviewable draft. Preview, publish the revision, and separately activate it. Return to native shell changes the active reference without deleting custom source, but pages requiring a shared header can block it.

A shell rollback does not restore page bodies, roots, settings, or translations. For a wider incident, request administrator-assisted snapshot assessment. See templates and reusable content, design and styling, and saving and recovery.