Sitecommand
Sign inStart free

Safe updates

WordPress updates that roll back when they break a site

Every update gets a restore point and a check. When a release breaks a site, the old version is back before anyone notices.

Start free Read the setup guide
client-shop.com.auRolled back

ELEMENTOR PRO · UPDATE AND VERIFY

  1. Restore point saved02:14:08
  2. Updated 3.25.1 → 3.26.002:14:19
  3. Front page check: 50002:14:30
  4. Rolled back to 3.25.102:14:41

The site never stayed broken. The new version waits until the plugin's next release.

On every update

Saved, updated, checked. Or put back.

  1. 01

    Restore point

    The installed version is copied aside on the site before anything changes.

  2. 02

    Update

    WordPress's own updater runs it, so active plugins stay active.

  3. 03

    Check

    The front page must load, the site must answer, and the page must still look like itself.

  4. 04

    Roll back

    If the check fails, the old version goes back and switches on again. You get the reason.

The whole fleet

One list of every plugin, on every site.

See that a plugin is behind on 14 sites, which versions are vulnerable, and update a selection or everything, starting with one site as a test.

  • Vulnerable versions marked, with the version that fixes them
  • Update by hand, security fixes only, or everything, in a weekly window
  • Exclude a plugin from schedules and keep updating it by hand
Updates · 40 sitesUpdate 32 selected
SOFTWAREVERSIONSITES
Yoast SEO24.1 → 24.314
WooCommerce9.4.2 → 9.5.06
Contact Form 7vulnerable5.9.8 → 6.0.19
WordPress7.1.3 → 7.1.43

Why it matters

Updating without fear.

Updating by hand

One site at a time, in wp-admin

A broken release found by the client

Rolling back means FTP and a backup

Updates put off, sites fall behind

With Sitecommand

Forty sites from one page

Checked straight after, on every site

Rolled back by itself, with the reason

Security fixes first, on a schedule

FAQ

Questions

How does it know an update broke the site?+

Straight after the update it loads the front page, asks the connector for a signed status and compares the page with how it looked before. If any of those fail, it restores the previous version and tells you why.

Where is the restore point kept?+

On the site, in a protected folder inside uploads. Sitecommand does not store your sites' files.

Does WordPress core roll back too?+

No. Core updates ask you to confirm you have a recent backup first: a full copy of WordPress is too large to keep on the site, so core has no automatic rollback.

Can I keep a plugin from updating, or only take security fixes?+

Yes. Choose by hand, security fixes only, or everything in a weekly window, and exclude any plugin from schedules.

Do active plugins stay active after updating?+

Yes. Plugins are updated in place and switched back on after a rollback.

Keep reading

Related

Rescue modeWhen a plugin or theme causes WordPress's critical error page, Fix site switches it off while the site is still down. No FTP, no host panel, no recovery email.Read Uptime monitoringUptime checks every few minutes, SSL and domain expiry, and vulnerable plugins. Alerts go to Slack, Discord, Telegram or a webhook, worst problems first.Read Malware sweepA weekly sweep of files, users and settings on every site. Cleanup moves files to quarantine instead of deleting them, and every step can be undone.Read

The sites keep running.
So do you.

Connect your first site in two minutes. Free during launch.

Start free How to connect a site