When a site breaks the moment a plugin updates, that update is the prime suspect — but not always the whole story. The new version can expose an incompatibility that already existed with your PHP version, theme or another plugin. Here is how to recover service and then make the next update safe.
Step 1 — Get back in without losing the evidence
If the site still loads, deactivate the updated plugin from the admin. If it does not, go to SFTP or the file manager and rename that plugin’s folder inside /wp-content/plugins (for example woocommerce to woocommerce_off). WordPress treats it as deactivated and the site should return. Note the plugin name and version before you change anything — you will need them.
Step 2 — Confirm it really is that plugin
Read /wp-content/debug.log (enable WP_DEBUG_LOG as above) or the PHP error log. If the fatal error names the plugin you just updated, you have your answer. If it names a different component, the update simply pushed an already-fragile setup over the edge — for instance a plugin that now requires a newer PHP version than your server runs.
Is your website affected right now?
Send the URL and the symptom you can see. Jordi Ensenyat reviews the case personally and defines the scope and quote before anything is changed. This form never asks for passwords.
Step 3 — Choose the right recovery, not just the fastest
- Roll back the version if the update introduced the bug — but only after checking whether it also ran a database migration. Rolling back a plugin that already upgraded its data can corrupt it.
- Fix the compatibility — update PHP, the theme or the conflicting plugin — if the new version is correct and your environment was behind.
- Replace the plugin if it is abandoned and no longer maintained.
Renaming the folder is an emergency stop, not a repair: a deactivated payment, booking or membership plugin means those features are now offline.
Step 4 — Make the next update safe
Once stable, reproduce the update on a staging copy or with a fresh backup in hand. Confirm which version works, what condition caused the failure, and test the specific feature the plugin controls — not just the home page. For business-critical plugins, set up a staging site so a bad release never hits production first.
Preserve first
Before rolling anything back, snapshot the current state. A rollback is itself a change, and you want to be able to undo it if it turns out the data had already migrated.
When to escalate
Get help if the plugin controls checkout or memberships, if there is no backup, or if a rollback risks the database. Send the plugin name, the version, the error and what the plugin does, and the safest recovery path can be planned before touching the live site.
EVIDENCE-LED WORDPRESS RECOVERY
Recover from a plugin update and make the next update safer
In urgent website repair and WordPress recovery, the visible symptom may be far from the cause. The objective is to restore the affected journey without gambling with the rest of the site. Rolling back a plugin can restore service, but it may also reverse a database migration or reintroduce a security issue. The right recovery route depends on the error, the plugin’s data changes and the compatibility of WordPress, PHP, the theme and connected extensions.
What we verify
- The complete journey, not only the screen where the error appears
- External dependencies, logs and evidence before configuration changes
- Fatal errors and compatibility notices introduced by the update
- Whether the plugin changed database schema, settings or generated assets
- Available backup, rollback package and vendor-supported version path
- The feature controlled by the plugin plus wider regression checks
What a verified outcome means
Close-out documents the cause found, the change applied and the tests performed. The result must be observable and repeatable—not a feeling that it “seems to work”.
BEFORE THE ASSESSMENT
Common questions about this WordPress incident
How do you verify that the problem is genuinely resolved?+
The affected journey is reproduced, its dependencies are checked and post-change evidence is recorded.
Is it safe to rename the plugin folder?+
It can disable a failing plugin in an emergency, but it is not a complete repair and may leave dependent features or migrations unresolved.
Can I simply install the previous plugin version?+
Sometimes, but database changes and security advisories must be considered. A rollback should match the plugin’s supported downgrade path.
How do I prevent the next update breaking production?+
Use a current backup, staging test, compatibility review and a defined rollback route for business-critical plugins.