ReleaseWPChangeSync 2.0 is here →
Guides/Template Versioning and Rollback

Template Versioning and Rollback

Use template snapshots to recover from bad imports, accidental edits, or failed releases.
Updated 5 June 2026·Task guide

Outcome

You can inspect template version history, save manual snapshots, restore a known-good version, and understand when WPChangeSync creates automatic versions.

Video walkthrough

▶

Video walkthrough coming soon.

The YouTube embed will appear here.
Risk level

Medium. Restores can replace current template state. Save current state before rollback.

Before you start

  • Template versioning is enabled in Config -> General.
  • You know the template ID or can find the template in the Library.
  • You have not cleared versions for the affected template.

Steps

  1. Save a version before risky work
    Create a manual snapshot before large template edits or imports.
  2. Review version history
    Open template versions from the UI or list them with WP-CLI.
  3. Restore the right version
    Restore the selected version; WPChangeSync saves the current state before restoring.
  4. Verify in Bricks and front end
    Open the template in Bricks and inspect the rendered page.
  5. Keep versions until release acceptance
    Do not clear versions until the release window has passed.

Screenshots

Template Versioning & Rollback
Template Versioning & Rollback
wp wpchangesync templates versions 123nwp wpchangesync templates save-version 123 --reason="Before production deploy"nwp wpchangesync templates restore 123 v_1705123456_abcdnwp wpchangesync templates clear-versions 123 --yes
Backups and versions work together
Bricks templates use the native WPChangeSync versioning system for backup-before-overwrite flows; other post types use JSON snapshot meta.

Verify and recover

Use the versioning commands to list, save, restore, and clear template snapshots. Always verify the restored template in Bricks and keep the previous state until the release is accepted.