11 WordPress ServicesView all
8 industry verticalsAll industries
12 UK locationsAll locations
Home/Blog/Troubleshooting
Troubleshooting8 November 2026· 6 min read

A WordPress Plugin Update Broke My Site: How to Recover

You clicked Update on a plugin and your site immediately went down. Here is how to identify which plugin caused it, deactivate it without admin access, and roll back to the previous version.

You clicked Update on a plugin — maybe several at once — and immediately your WordPress site went down or stopped working correctly. This is fixable in almost every case without data loss. The key is knowing how to isolate which plugin caused the problem and how to deactivate it quickly, even when the admin dashboard is inaccessible.

Why plugin updates break WordPress sites

Plugin conflicts after an update are caused by one of four things: the updated plugin introduced a PHP function that conflicts with another active plugin; the update requires a newer PHP version than your server is running; the update changed something your active theme depends on; or the new version of the plugin has a bug the developer has not yet caught and released a fix for.

Step 1: Deactivate the plugin immediately

If you still have admin access, go to Plugins and deactivate the plugin you just updated. If admin is inaccessible, connect via FTP or your hosting file manager, navigate to /wp-content/plugins/ and rename that specific plugin's folder — for example, change contact-form-7 to contact-form-7-old. WordPress automatically deactivates any plugin whose folder is renamed.

Step 2: Enable debug mode to see the exact error

Open wp-config.php via FTP and set WP_DEBUG to true temporarily. This shows the specific PHP fatal error on screen, including the file and line number. It will confirm which plugin is causing the issue — a PHP version incompatibility will state the specific function that is missing, and a conflict with another plugin will name both.

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', true);

Step 3: Roll back to the previous version

Once the site is accessible again, roll back the offending plugin. With admin access, install WP Rollback — it adds a Rollback link to every plugin in your Plugins list. Without admin access, go to the plugin's page on wordpress.org, scroll to the Developer tab, download a previous version as a zip file and upload it via FTP, overwriting the current files.

Step 4: Report the conflict and check for a patch

Most plugin developers fix known compatibility issues within days of a report. Check the plugin's Support forum on wordpress.org — if others have the same issue, there may already be a workaround or an ETA for a fix. Submit your own report with your conflicting plugin name, PHP version and WordPress version.

ImportantNever update plugins directly on your live site without a backup. A one-click update takes three seconds; a site recovery without a backup can take hours. Our WordPress maintenance plans include automated daily backups stored off-site and staged plugin updates tested before they touch the live site.

Frequently asked questions

What should I do first when a plugin update breaks my WordPress site?+

If you can still access wp-admin, go to Plugins and deactivate the plugin you just updated. If admin is inaccessible, connect via FTP or your hosting file manager and rename that specific plugin's folder inside /wp-content/plugins/ — WordPress automatically deactivates any plugin whose folder is renamed.

How do I roll back a WordPress plugin to a previous version?+

Install the WP Rollback plugin if you have admin access — it adds a Rollback link to every plugin and lets you choose a previous version from the full version history. Without admin access, download the previous version from the plugin's changelog on wordpress.org and upload it via FTP, overwriting the current files.

How do I identify which plugin caused my WordPress site to break?+

Enable WP_DEBUG in wp-config.php to see the specific PHP fatal error — the error message names the file and line number, which usually includes the plugin's folder name. If you updated multiple plugins at once, deactivate them all via FTP, then reactivate one at a time, testing your site after each, until the problem returns.

How can I prevent plugin updates from breaking my site in future?+

Always test plugin updates on a staging environment before applying them to the live site. Update one plugin at a time rather than all at once. Take a full site backup before any update session. Our WordPress maintenance plans handle all of this — staged updates, automatic backups and rollback if anything fails.

Related service

If you are updating plugins directly on a live site without a staging environment, our maintenance plans handle all updates — staged, tested and automatically rolled back if something breaks.

WordPress Maintenance Plans →

Next article

Troubleshooting

WordPress 404 Errors After Migration: Why Every Page Breaks and How to Fix It

→
← All articles