WordPress broken after a plugin update: what now?

It tends to happen on an ordinary morning. You click "Update" in the dashboard, and shortly after someone calls because the website will not load. Or the contact form stops sending emails, the shop loses its prices, the layout falls apart. For a small business that hurts, because enquiries and orders come in through exactly this site.

The good news: almost always, nothing is lost. After the update, the plugin simply no longer gets along with your PHP version, your theme or another plugin. Below are the first-aid steps I use on support tickets myself, in the order I work through them.

Step 0: Stay calm and delete nothing

Before you click anything:

• Don't delete anything. Removing the plugin through WordPress can wipe its settings too.
• Don't keep updating. More updates change the state and make troubleshooting harder.
• Write down what happened. Which plugin did you update, at what time, what error do you see? A screenshot helps a lot.

Step 1: Use recovery mode

Since version 5.2, WordPress has a built-in recovery mode. When a fatal PHP error occurs, it emails the admin address with the subject "Your Site is Experiencing a Technical Issue" and a special login link.

Here is what to do:

1. Check the admin inbox, including spam.
2. Click the link in the email and log in.
3. WordPress shows you which plugin caused the error. Deactivate it there.
4. Check the site in a private browser window.

No email? That happens, for example when the site's own mail sending is broken. Move on to step 2.

Step 2: Rename the plugin via SFTP or FTP

If you cannot reach the dashboard, deactivate the plugin directly on the server. You need your hosting SFTP credentials and a client such as FileZilla or Cyberduck. Many Swiss hosts also offer a file manager in their control panel.

1. Connect to the server and open wp-content/plugins/.
2. Find the folder of the plugin you updated last, for example contact-form-7.
3. Rename it, for example to contact-form-7-off.
4. Reload the site.

WordPress can no longer find the plugin and deactivates it automatically. Its settings stay in the database. If the site works again, you have found the culprit. If you are not sure which plugin it was, rename the whole plugins folder, check the site, then reactivate the plugins one by one.

Only rename the folder back once the problem is solved, for example when a fixed version of the plugin is out.

Step 3: Turn on the debug log

To see what exactly is going wrong, use the debug log. The official guide is in the WordPress debugging documentation. Add these lines to wp-config.php, above the line "That's all, stop editing!":

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

Then load the broken page once. wp-content/debug.log now contains the error with file and line number. The path usually tells you which plugin is involved. Typical causes are an outdated PHP version or a function that another plugin or your theme expects.

Setting WP_DEBUG_DISPLAY to false keeps the errors hidden from visitors. Turn debugging off again when you are done and delete debug.log, since it can contain paths and other internal details.

Step 4: Roll back the plugin or restore a backup

If you really need the plugin, say for your shop or booking form, you have two options:

• Install the previous plugin version. For plugins from the official directory, older versions are listed on the plugin page under "Advanced View". For premium plugins, you usually find them in your account with the vendor. Treat this as a stopgap until the developer ships a fix.
• Restore a backup. Many hosts keep daily backups you can restore from the control panel. Watch which point in time you restore: orders, form entries or comments since that backup will be gone otherwise. For a shop, I prefer to restore only the files and leave the database alone when that is possible.

No backup at all? Then setting one up is the first job once the site is fixed.

Step 5: Test on staging first next time

The safest approach is not to apply updates straight to the live site at all. A staging environment is a copy of your site where you can test without risk. Many hosts offer it with one click.

My routine for client sites:

• A fresh backup before every update.
• Big plugins such as WooCommerce, page builders or forms get updated on staging first.
• Click through the key pages: home, contact form, cart, mobile view.
• Only then update live, and not on a Friday evening or right before a campaign.
• Check PHP and WordPress versions regularly so plugins are not running on outdated tech.

When to get help

Fixing it yourself makes sense when one plugin is clearly the cause and you have server access. Get help when:

• you have no SFTP or hosting access, or you are not comfortable using it,
• the error stays even with all plugins deactivated,
• a shop with live orders is affected,
• the database looks damaged or content is missing,
• unfamiliar files or admin accounts show up. Then it may be a hack rather than an update.

In those cases, a professional usually saves you time and stress, and lowers the risk of one wrong click making things worse.

Conclusion

A plugin update that takes WordPress down looks dramatic, but it is usually quick to fix: use recovery mode, otherwise rename the plugin via SFTP, find the cause in the debug log, and roll back to an older version or a backup if needed. With staging and backups in place, the next broken update never reaches your live site.

Stuck somewhere, or would you rather hand updates off? See how I handle WordPress support, or check the FAQ for process and pricing. And if it is just a small fix, just drop me a line. I will tell you for free how much work it is.

Related: if you are working on your site anyway, have a look at the Swiss data protection checklist, since many plugins process personal data. And if you are wondering whether to repair or rebuild: What does a website cost in Switzerland?

Frequently asked questions

Will I lose data if I rename a plugin folder via SFTP?

No. Renaming the folder only deactivates the plugin. Its settings stay in the database as long as you do not delete the plugin from within WordPress.

Should I turn off automatic plugin updates?

Not across the board. Security updates matter. For big plugins such as shops, page builders or forms, it is worth testing updates on staging first and only then applying them live.

What does it cost if you fix my site?

CHF 45 per hour, billed in 15-minute increments. Before I start, I tell you for free how much work it will be.

How fast can you help?

You get a reply with an estimate within 4 working hours. If the site is completely down, we can arrange a short-notice fix.