Review version history and recover an edit
Inspect earlier saved content and, when authorized, restore a suitable version.
Review version history and recover an edit
Inspect earlier saved content and, when authorized, restore a suitable version.
You need
Access to the content and its history, an existing saved record, and agreement with other editors before restoring. This is content recovery, not recovery of unsaved typing.
Steps
Open the page history
Open the correct existing page and select History.
Locate the version
Expand Version History if it is collapsed. Check the version number, time, and Saved by details to locate the intended version.
Review the version
Select View version with the eye icon or Compare with current with the comparison icon. The view can contain technical content rather than a rendered page. Ask your agency if it is not clear what will change.
Choose the version to restore
After you agree to the recovery, choose Restore version with the restore icon, or select Restore This Version from the open version view.
Confirm the restore
Read Restore Version carefully. The action replaces the current stored content. Select Cancel if you are unsure. Select Restore only when authorized.
Review the restored content
Wait for Version restored, then reopen and review the content. Check Site Preview at Desktop and Mobile sizes.
Send Development changes for review
For Development, send the recovery to your agency for publication review. A restore in Live can change the public content.
The selected saved version replaces the current stored content for that record in the environment you are editing. It is not a selective undo of one sentence.
Other content
Existing WebApp items have a History tab. Blog editors and Menu Builder can show Version History on the editing screen. Use the same review-and-confirm approach wherever the panel is present.
No version history yet means the panel has no earlier versions to offer. It does not mean a deleted file or unsaved edit can be recovered. Ask your agency before taking further action.
Save or otherwise resolve local unsaved work before attempting a restore. Coordinate with other editors so you do not overwrite newer approved work. Do not assume every field, file, or related record is included in a particular history view. Inspect the version and ask your agency if you are uncertain. History is not a substitute for checking the result.
Screenshot S19: Page History with safe version rows and review and restore icons.
Capture instructions: manifest S19.