Skip to content

Restore

Restore downloads an archive from your storage and writes it back onto the WordPress server. ConstellaWP only presigns URLs and tracks the job. The agent must report the restore capability (current ConstellaWP Agent).

Owners and admins start restore from the site Backups list. Members cannot.

A full restore replaces:

  • WordPress core, themes, plugins, and uploads
  • The entire database (posts, users, WooCommerce orders, and everything else created after the backup are lost)

The site is put in maintenance mode for the duration.

Every archive records the layout it uses and the oldest agent able to restore it. ConstellaWP checks both before queueing the job, so you get a clear message instead of a job that fails halfway.

  • Backups tagged Legacy format were produced before agent 1.5.0, in a layout current agents no longer read. The Restore button is hidden. Download the archive and restore it by hand if you still need it.
  • A site running an agent older than the archive requires is refused with the version to install. Update the agent from the site’s plugins list, then restore again.

The confirmation dialog defaults to Create a safety backup first. ConstellaWP uploads a snapshot of the current site to your destination before anything is overwritten. Safety backups are tagged in the list and kept for 7 days.

If you turn the checkbox off, you must type the site domain to confirm. Without a safety backup, a restore that fails halfway can leave the site unusable with no automatic rollback.

  • Restore is blocked while another backup or restore job is queued or running on that site.
  • The destination that holds the archive must still exist and accept downloads. If you deleted the destination in ConstellaWP, restore cannot presign a GET URL.
  • Download URLs for restore stay valid long enough for the safety backup step (about 2 hours), not the 15-minute window used for manual downloads.

A restore puts the site back to a state its caches know nothing about, so the agent finishes the job with a cleanup pass, still under maintenance mode:

  • WordPress database upgrade. The dump carries the db_version of the moment the backup was taken. When the core files on disk are newer, the agent runs the migration itself, so wp-admin no longer greets you with Database update required.
  • Permalinks. Rewrite rules are dropped and rebuilt on the next page load.
  • Server-side caches. Object cache (Redis, Memcached), PHP OPcache, and WordPress update checks.
  • Page builders and cache plugins. Elementor (the equivalent of Clear Files & Data), Divi, Beaver Builder, Bricks, WP Rocket, LiteSpeed, W3 Total Cache, WP Super Cache, WP Fastest Cache, Autoptimize, SG Optimizer, Breeze, Cache Enabler, Nginx Helper, and wp-content/cache.
  • Hosting cache. If the site is linked to a hosting account whose provider supports it (Cloudways, WP Engine), ConstellaWP purges the server cache right after the job completes.

The Backups page then shows a Restore completed card listing exactly what was cleaned and what is left for you. It stays for 24 hours or until you dismiss it.

This requires ConstellaWP Agent 1.4.0 or later. Older agents restore fine but clean nothing, and the card only shows the manual checklist.

  1. Watch the job until success.
  2. Load the front-end and wp-admin.
  3. Read the Restore completed card and go through what it lists as still manual.
  4. If you used a safety backup and the result is wrong, restore that safety backup the same way.

Hosting-provider snapshots (cPanel lists, Cloudways) are not restored from this page. Use the host panel for those; ConstellaWP shows them as information only.

If the site looks broken, stale, or half-styled once the restore is done, it is almost always a cache the agent cannot reach from inside WordPress.

Your browser. Hard-refresh the page or open it in a private window before anything else.

Your CDN. Cloudflare, Fastly, Bunny, and the like keep serving the pre-restore HTML and assets. Purge everything from their dashboard. ConstellaWP does not touch CDNs.

Your host. If the site is not linked to a hosting account in ConstellaWP, purge the server cache from the host panel yourself (Varnish on Cloudways, the cache tab on WP Engine, LiteSpeed cache on cPanel hosts).

Your page builder. The agent clears their caches, but a version mismatch or a deactivated plugin can leave stale files behind. Regenerate them by hand:

  • Elementor: Elementor > Tools > Regenerate CSS & Data, then Sync Library
  • Divi: Divi > Theme Options > Builder > Advanced > Clear cache
  • Bricks: Bricks > Settings > Maintenance > Regenerate CSS
  • Beaver Builder: Settings > Beaver Builder > Tools > Clear cache

Critical CSS. Optimization plugins and some themes store their own generated critical CSS, which is not covered by a regular cache purge. Clear it from their own settings.

The database update screen. The restore summary tells you whether the migration ran, was scheduled for the next visit to the site, or has to be confirmed by hand. If wp-admin still asks to update the database, confirm the update it offers: it is the normal WordPress migration, run with the right code.