Changes and publishing
Backups, restore points and rollback
The three kinds of safety net and when each one helps.
WPBuild has three different safety nets. They protect different things.
| Backup before a send | Restore point | Snapshot | |
|---|---|---|---|
| Protects | Your live site | Your staging site | Nothing: it's a picture |
| Taken | Automatically, before every send | By the AI, before it starts each request | After changes and sends, or with Refresh snapshots |
| Contains | The whole live database, the live files about to be replaced, and the rows about to change | Staging's pages, posts and key settings | Screenshots of staging and live, desktop and mobile |
| Used by | Roll back on the Live history tab | The AI, when you ask it to undo something on staging | The Snapshots tab, for comparing |
Rolling back a send
- Open the Live history tab. Every send is listed, newest first.
- Press Roll back on the send you want to undo.
- WPBuild puts back the live files it replaced, removes files that send added, restores the pages, posts and settings it changed, and removes pages it added.
Rolling back restores what the send changed, as it was before. If someone edited one of those same pages on the live site after the send, that later edit is lost too. Orders, comments and anything the send didn't touch are not affected.
Users and plugin switches sent from Users, plugins and theme appear as their own entries in Live history and can be rolled back the same way.
Undoing a change on staging
Before you've sent it, just ask: "Undo the last change to the home page". The AI can use the restore point it saved. Or, to start again from the live site, use Copy live again (this replaces all of staging).
What these are not
- Not a full backup service for your live site. Backups are taken when you send changes from WPBuild. They don't cover edits made directly in WordPress, new orders or uploads between sends.
- Not a download. Backups are kept by WPBuild for rolling back; there's no button to download them. Contact support if you need a copy.
For day-to-day protection of a busy site, keep your host's or a plugin's regular backups as well.