You clicked “Update” and now your site is broken. Maybe it’s showing errors, maybe the layout is mangled, or maybe it won’t load at all. WordPress updates are essential for security and performance, but when they go wrong, they can bring your entire site down.

Don’t panic. In most cases, you can roll back to a working state and get your site back online quickly. Here’s how.

Why Do WordPress Updates Break Sites?

Understanding why updates cause problems helps you prevent them in future. The most common reasons are:

• Plugin incompatibility: A plugin update may not be compatible with your current version of WordPress, your theme, or other plugins. Plugin developers don’t always test against every possible combination.
• PHP version mismatch: Newer versions of WordPress and plugins sometimes require newer PHP versions. If your hosting is running an older PHP version, updated code may not work correctly.
• Theme conflicts: WordPress core updates occasionally change how themes work under the hood. If your theme hasn’t been updated to accommodate these changes, things break.
• Interrupted updates: If your internet connection drops or your server times out during an update, files can be left in a half-updated state, which is one of the worst scenarios.

Option 1: Restore from a Backup (The Best Option)

If you have a recent backup from before the update, this is by far the safest and quickest way to get back to a working site. Here’s how, depending on your backup method:

If your hosting provider takes automatic backups: Log into your hosting control panel and look for a backup or restore option. Most quality hosts keep daily backups for at least 14 days. Select a backup from before the update and restore it.

If you use a backup plugin like UpdraftPlus: If you can access your WordPress admin panel, go to Settings and then UpdraftPlus. Find the backup from before the problematic update and click Restore. Choose to restore all components: plugins, themes, uploads, database, and other files.

If you can’t access wp-admin: You’ll need to restore manually via FTP and phpMyAdmin. This is more technical, so if you’re not comfortable with these tools, it may be best to get professional help.

Once restored, do not immediately run the same update again. First, find out why it broke and address the underlying issue.

Option 2: Roll Back a Plugin Using WP Rollback

If the problem was caused by a specific plugin update and your site is still accessible, the WP Rollback plugin is a lifesaver. Install it from the WordPress plugin repository, then go to your Plugins page. You’ll see a “Rollback” option next to each plugin. Click it to choose which version you want to revert to.

Select the version that was running before the problematic update and click “Rollback.” The plugin will download and install the previous version automatically.

A word of caution: Only roll back to the immediately previous version. Going back further can introduce other compatibility issues. And remember, running an older version of a plugin means you may be missing security patches, so this should be a temporary measure while you sort out the compatibility issue.

Option 3: Manual Rollback via FTP

If your site is completely inaccessible, you’ll need to use FTP to make changes directly on the server. This approach works for rolling back plugins, themes, or even WordPress core.

To roll back a plugin: Connect to your site via FTP. Navigate to wp-content/plugins and delete the folder for the problematic plugin. Then download the previous version from wordpress.org/plugins (click “Advanced View” to see previous versions) and upload it to the plugins folder.

To roll back a theme: Navigate to wp-content/themes and replace the theme folder with the previous version. If you’ve made customisations, be careful not to overwrite those files.

To roll back WordPress core: Download the previous version from wordpress.org/releases. Upload the wp-admin and wp-includes folders, overwriting the existing ones. Never overwrite wp-content or wp-config.php.

Preventing Update Disasters in Future

Prevention is always better than cure. Here are the habits that will save you from update headaches:

1. Always back up before updating. This is the golden rule. If you have a backup, the worst that can happen is a few minutes of downtime while you restore. Without a backup, a bad update can mean hours or days of work to fix.
2. Use a staging environment. A staging site is a copy of your live site where you can test updates safely. If an update breaks the staging site, your live site is unaffected. Many hosting providers offer one-click staging environments.
3. Update one thing at a time. When WordPress shows you ten available updates, resist the temptation to click “Update All.” Update plugins one at a time and check your site after each one. This way, if something breaks, you know exactly which update caused it.
4. Keep everything in sync. Running the latest WordPress core with outdated plugins is a recipe for trouble. Try to keep your core, plugins, and themes all current.
5. Read the changelog. Before updating, click “View version details” to see what changed. If a major update mentions “breaking changes” or requires a newer PHP version, proceed with extra caution.

When Rolling Back Isn’t Enough

Sometimes the damage from a failed update goes deeper than simply reverting files. Database changes, corrupted uploads, or cascading conflicts between multiple updates can create situations where a simple rollback doesn’t fully resolve the issue.

If you’ve tried rolling back and your site is still misbehaving, or if you’re not confident making these changes yourself, that’s exactly what we’re here for. We deal with botched WordPress updates every week and we know how to untangle even the messiest situations.

Get in touch and we’ll get your site back to normal.