Blog October 27, 2026 16 min read Reviewed by real people

A WordPress or plugin update broke my site: what to do, in order

Last updated: November 16, 2026 · By the Revive Guard team. Added the ten-minute wait for a stuck maintenance message, how to tell which update broke the site, and what to do first when a WordPress update breaks it. Also covers WordPress core updates, theme updates, WP-CLI commands and what to send a developer or […]

A WordPress or plugin update broke my site: what to do, in order

Last updated: November 16, 2026 · By the Revive Guard team. Added the ten-minute wait for a stuck maintenance message, how to tell which update broke the site, and what to do first when a WordPress update breaks it. Also covers WordPress core updates, theme updates, WP-CLI commands and what to send a developer or plugin support.

You clicked Update, and now the site shows a blank page, a “There has been a critical error on this website” message, or a layout that has fallen apart. This is one of the most common ways a WordPress site breaks, and it is usually fixable in a few calm steps. The order matters, because the wrong first move (restoring an old backup on a busy store, for example) can lose data that the plugin never touched.

Short answer: (1) stop clicking Update and note whether this was WordPress itself, a plugin or a theme; (2) check wp-admin and whether WordPress emailed a recovery link; (3) use recovery mode to deactivate what failed, or rename its folder if you can’t log in; (4) if you see “Briefly unavailable for scheduled maintenance,” start at stuck maintenance mode; (5) for a core update, also see If it was a WordPress core update; (6) roll back just the broken piece, or restore a pre-update backup only if nothing important changed since; (7) test the pages that make you money before you call it fixed.

First, 60 seconds of triage

Stop clicking Update. Screenshot or copy the exact error message and write down what you updated and when. Then answer three questions — they tell you which step to start from.

Question If yes If no
Did WordPress email the site admin about a “technical issue”? Start at recovery mode. The email usually names the plugin. Check spam, then try recovery mode anyway, or go to disabling from your files.
Can you still log in to wp-admin? Deactivate the plugin you just updated, then decide on rollback. Use your host’s file manager or SFTP.
Is the site down, or does it just look or behave wrong? Down (blank page, critical error): fix first, investigate later. Broken layout, checkout or form: note exactly what is wrong and when it started; that’s what a developer or the plugin’s support team will ask for.

Also note which plugins you updated and roughly when. If you updated ten plugins at once, the culprit is one of those ten, and that’s the list you will work through.

What you see, and where to start

The message on screen usually tells you which kind of problem you have. Find yours, then jump to the step that fixes it.

What you see What it usually means Start here
“There has been a critical error on this website” A fatal PHP error, often from the plugin you just updated. Recovery mode, or disable it from your files if you can’t log in
A blank white page Also usually a fatal error, just with error messages hidden. Disable the plugin from your files
“Briefly unavailable for scheduled maintenance. Please check back in a minute.” that doesn’t go away The update stopped before WordPress could take the site out of maintenance mode. Delete the .maintenance file
Layout, menus or fonts broken right after a theme update The theme changed, or a child theme no longer matches it. If it was a theme update
Problems started right after WordPress itself updated Usually a plugin or theme that isn’t ready for the new version; sometimes a core update that didn’t finish. If it was a WordPress core update
Site loads, but checkout, a form or a page builder no longer works A conflict that doesn’t crash the site, so WordPress won’t catch it. Roll back that plugin

Stuck on “Briefly unavailable for scheduled maintenance”

While it updates, WordPress puts a file called .maintenance in the site’s root folder (the one that holds wp-config.php) and shows visitors that message. If the update is interrupted, the file can be left behind.

Before you delete anything: WordPress core stops honouring that file once the timestamp inside it is more than ten minutes old (wp_is_maintenance_mode() in wp-includes/load.php). So if the notice appeared only a few minutes ago, wait up to ten minutes and reload in a private window — the site often comes back on its own. If it is still stuck after that, delete the file.

The WordPress common errors guide gives the fix: connect with your host’s file manager or SFTP and delete .maintenance. Files starting with a dot are often hidden, so turn on “show hidden files” if you can’t see it. If you use WP-CLI, wp maintenance-mode deactivate does the same thing.

Clearing the notice is not the whole job. An interrupted update can leave a plugin or core files half-replaced. Go to Dashboard → Updates and re-run anything still listed, or reinstall / roll back the plugin that was updating when it stuck.

Step 1: Use WordPress recovery mode

Since WordPress 5.2, when a plugin or theme causes a fatal PHP error, WordPress pauses it for your admin session and emails the site’s admin address a special login link. According to the WordPress.org recovery mode documentation, you log in through that link, look for the notice that names the failed plugin, deactivate it under Plugins, then click “Exit Recovery Mode” and check the site normally.

Two practical notes. The email is sent from your server, so it often lands in spam or never arrives if the site’s email isn’t set up well. And recovery mode only helps with fatal errors. If the update broke a layout or a checkout without crashing the site, there is no email and nothing is paused, so go straight to Step 3.

Step 2: Can’t log in? Disable the plugin from your files

You don’t need wp-admin to switch a plugin off. Open your host’s file manager (or connect by SFTP), go to wp-content/plugins/, and rename the folder of the plugin you just updated, for example contact-form-plugin to contact-form-plugin-off. WordPress can no longer find it, so it is deactivated. Your settings stay in the database.

If you don’t know which plugin it was

Rename the whole plugins folder (to plugins-off). This switches every plugin off at once, which is the method the WordPress developer docs on common errors describe for the white screen. If the site loads, rename the folder back to plugins; the plugins stay deactivated, and you turn them on one at a time in wp-admin until the error comes back. The last one you activated is the cause.

On a store or booking site, every minute with plugins off can mean missed orders, so if you can identify the single plugin, disable only that one.

If you or your host can use WP-CLI

WP-CLI is WordPress’s command-line tool, and many hosts include it over SSH. It does the same jobs faster, without needing wp-admin. Replace plugin-name with the plugin’s folder name and the version number with the last one that worked:

  • wp plugin deactivate plugin-name --skip-plugins switches off one plugin; --skip-plugins stops plugins loading while the command runs, so the broken one can’t crash it.
  • wp plugin deactivate --all --skip-plugins switches them all off if you don’t know which one it was.
  • wp plugin install plugin-name --version=1.2.3 --force puts back an earlier version of a WordPress.org plugin over the current one.

The WP-CLI plugin command docs list every option. If commands like these are unfamiliar, use the file method above instead; it reaches the same result.

If it was a theme update, not a plugin

The same steps work for themes, in a different folder. If you can log in, switch to a default WordPress theme (such as a recent “Twenty” theme) to confirm the theme is the cause. If you can’t, the WordPress common errors guide says to rename the active theme’s folder in wp-content/themes/.

If your site uses a child theme, updating the parent theme doesn’t touch the child theme, but changed parent templates can stop matching the child theme’s copies. Roll the parent theme back the same way as a plugin, then ask whoever built the child theme to update it. If someone edited the parent theme’s files directly, an update overwrites those edits; a backup from before the update is the only way to get them back.

If it was a WordPress core update

When trouble starts right after WordPress itself updates, WordPress is rarely the broken part. More often a plugin or theme isn’t ready for the new version yet, so start the same way: try recovery mode, or disable plugins from your files, and see whether the site comes back. Then roll back or wait for a fix for that one plugin or theme.

If the core update stopped partway, you may be stuck on the maintenance message (delete the .maintenance file) or see errors from WordPress’s own files. Run the update again from Dashboard → Updates, where you can also re-install the current version. If you can’t reach the dashboard, WordPress.org’s Updating WordPress guide explains replacing the wp-admin and wp-includes folders by hand. Never delete your wp-content folder or wp-config.php.

With WP-CLI, wp core verify-checksums compares your core files with the checksums WordPress.org publishes and changes nothing. If it passes, the core files are fine and the cause is a plugin or theme. If it fails, wp core download --version=YOUR-VERSION --skip-content --force puts back clean core files for the version you already run, without touching your themes and plugins.

Going back to an older WordPress version is a last resort. WordPress.org’s guide says you can restore your backup and use files from the release archive, but newer versions carry security fixes, so treat a downgrade as a short stopgap while the plugin or theme catches up.

Step 3: Roll back the plugin, or restore the whole site?

Once the site is back up, you have two ways to get the plugin working again: put the previous version of that one plugin back, or restore the whole site from a backup taken before the update. The right choice depends on what has changed on the site since then.

Situation since the update Better option Why
New orders, bookings, form entries, comments or sign-ups Roll back the plugin only A full restore takes the whole database back in time and can erase that new data.
Nothing has changed, and you have a backup from right before the update Restore the site, or the plugin files only if your backup tool allows it Cleanest way back to a known working state.
The update also changed the plugin’s database tables (common with stores, forms and page builders) Restore a pre-update backup, or ask the plugin’s support first Putting old plugin files back does not undo database changes, a caveat raised in this WordPress Stack Exchange thread.
Your only backup is days or weeks old Roll back the plugin; keep the old backup as a last resort An old backup brings back old content, old plugin versions and any old problems.

Roll back a free plugin from WordPress.org

Download the previous version from the plugin’s page on WordPress.org (the “Advanced View” area lists earlier versions), then in wp-admin go to Plugins, Add New, Upload Plugin, and choose “Replace current with uploaded” when WordPress asks. A rollback plugin such as WP Rollback does the same job for WordPress.org plugins.

Roll back a premium plugin

Log in to the developer’s site, download the previous version from your account, and upload it the same way. If they don’t offer older versions, their support team usually can.

Restore from a backup

Use your backup tool or your host’s restore option, and pick the most recent point before the update. If you’re unsure whether the backup is complete or where it’s stored, our guide to off-host, verified backups explains what to check.

Either way, leave that plugin’s update on hold until its changelog or support forum shows a fix. Updating again straight away usually breaks the site the same way.

Step 4: Check the site properly before you call it fixed

  • Clear your caching plugin, your host’s cache and any CDN cache, then load the site in a private window.
  • Test the pages that matter: home, a key service or product page, the contact form (send a real test), checkout or booking if you have one, and the login.
  • Look at the site on a phone, not just a desktop.
  • Write down what broke, which plugin and version, and what you did. If it happens again, that note saves a lot of time.

What WordPress already does for you, and what it doesn’t

WordPress has quietly added some protection here. Since version 6.3, a manual plugin or theme update that fails is rolled back to the previous version. Since WordPress 6.6, if an automatic plugin update causes a fatal error, WordPress checks the site with a request to the home page, puts the previous version back, and emails the admin, as described in WordPress Trac ticket #58281.

That is useful, but it only catches updates that crash the site. An update that breaks your checkout, hides a form or scrambles a layout without a fatal error isn’t detected, and nothing is rolled back. It also doesn’t help if you’re on an older WordPress version. Someone still has to look at the site after updates.

What to send the developer or plugin support

A clear report gets a faster fix, whether it goes to the plugin’s support forum, your host or a developer. Include:

  • The plugin (or theme) name, the version you updated from and the version you updated to.
  • Your WordPress and PHP versions. Both are shown under Tools, Site Health, Info.
  • The exact error text or a screenshot, the page where it happens, and roughly when it started.
  • The error log line, if you can get it. Your host’s control panel often shows PHP error logs. The WordPress debugging guide explains how WP_DEBUG_LOG saves errors to wp-content/debug.log; turn it off again when you’re done.
  • What you’ve already tried (recovery mode, renaming the folder, rolling back) and what happened.

Don’t send passwords in a public support forum. If someone needs access, create a separate account for them and remove it when the fix is done.

When to stop and get help

  • Your store or booking system is down and every hour costs you money (our downtime cost worksheet helps you put a number on it).
  • You can’t identify the plugin, or the error comes back after you’ve rolled back.
  • You don’t have a backup from before the update.
  • You see things you didn’t change: new admin users, unfamiliar files, redirects to other sites. That points to a security problem, not a bad update; see what to do after a restore or hack.

If the site is down right now, the plugin’s own support forum and your host’s support are the fastest free places to start. A developer or maintenance team can take it from there. Already a Revive Guard client? Choose Site down or hacked on our contact form so it’s flagged as urgent. What happens next depends on your plan; the restore terms for each plan are set out on our WordPress maintenance service page.

How to stop the next update breaking your site

Most broken updates are easy to undo when the order was right: a fresh backup or snapshot, one important plugin at a time, a quick check of key pages, and a rollback ready. We cover that routine step by step in the safe-update section of our WordPress maintenance checklist. If you’re weighing a separate staging copy against snapshot and rollback, Pillar 3 of our security, updates and backups guide explains which fits which kind of site.

How Revive Guard handles this

On the Guard ($99/mo) and Shield ($179/mo) plans, our team runs weekly WordPress core, plugin and theme updates for you. We take a fresh snapshot before every change and roll back automatically if an update breaks something. Every rollback shows up in your activity log, and updates we hold back are listed in your monthly report. This is snapshot + rollback, not a staging site.

If the site goes down: Guard includes a priority restore from a clean backup, typically same-day, and Shield is restored within 4 hours of your report, in writing. Monitor ($49/mo) doesn’t run updates; it alerts you immediately, with a one-time restore available for $99 (no SLA). Full details are on plans and pricing and our WordPress maintenance service page.

FAQ

Why did a plugin update break my WordPress site?

Usually because the new version conflicts with another plugin, your theme, or your server’s PHP version, or because it has a bug the developer hasn’t fixed yet. Updating many plugins at once makes the cause harder to find.

Will deactivating or renaming a plugin delete its settings?

No. Deactivating or renaming the folder leaves the plugin’s settings in the database. Deleting the plugin from wp-admin can remove its data, depending on the plugin, so deactivate rather than delete while you troubleshoot.

Can I undo a plugin update without a backup?

Often, yes: upload the previous version of that plugin over the current one. It won’t undo database changes the update made, so for stores, forms and page builders, check with the plugin’s support first.

Should I turn off automatic plugin updates?

Not necessarily. Updates fix security holes, and WordPress 6.6 and later roll back an automatic update that crashes the site. What auto-updates can’t do is check your forms and checkout afterwards, so whoever looks after the site should still review it after updates.

How do I know which plugin caused the problem?

Check the recovery mode email or the notice in recovery mode, which usually names it. After automatic updates, WordPress also emails the admin address listing what updated and what failed — check spam. In the dashboard, Dashboard → Updates shows what is still waiting (anything missing from that list may already have updated), and Tools → Site Health → Info → Active Plugins lists each plugin with its version. On the plugin’s WordPress.org page, the sidebar shows when it was last updated and its “Requires PHP” version; a release from the day things broke, or a PHP requirement higher than your host runs, is a prime suspect. If you still are not sure, switch all plugins off and turn them back on one at a time until the error returns.

Why is my WordPress site stuck in maintenance mode after an update?

The update was interrupted before WordPress removed the .maintenance file from the site’s root folder. Delete that file with your host’s file manager or SFTP, or run wp maintenance-mode deactivate, then check that the plugin finished updating.

What if a theme update broke my site?

Switch to a default WordPress theme to confirm it, or rename the active theme’s folder in wp-content/themes/ if you can’t log in. Then roll the theme back. If you use a child theme, the child theme may need updating to match the new parent.

What if a WordPress core update broke my site?

Usually a plugin or theme isn’t compatible with the new version yet. Use recovery mode or disable plugins from your files to find it, then roll that one back or wait for its fix. If the core update didn’t finish, delete .maintenance and run the update again from Dashboard → Updates.

WordPress update broke my site — what do I do first?

Stop running more updates. Copy or screenshot the exact message and note whether WordPress core, a plugin or a theme updated. Start at 60 seconds of triage: use recovery mode or disable from your files, clear a stuck maintenance notice if you see one, then roll back or restore. If trouble started right after WordPress itself updated, follow If it was a WordPress core update.

Not sure your site would survive the next update?

Request a free evaluation. Within 48 hours, a real person sends written findings on your plugins, theme, hosting, SSL and domain, whether or not you join.

Not sure which side you’re on?

We’ll review your site and send written findings — usually within 48 hours. Free, no setup fee.

Get free evaluation ↗

Find out where your website stands, free.

A real person reviews your site and sends written findings — usually within 48 hours. No setup fee. Cancel anytime if you start a plan.

No setup fee Cancel anytime 7-day money-back guarantee Reviewed by a real person
Request a Free Evaluation
Secret Link