What do I do if a plugin update breaks my WordPress site?

A routine plugin update can occasionally break a site: a white screen, a broken layout, a checkout that stops working. It feels alarming, but the fix is usually quick if you know the steps. The key is to act calmly and not change several things at once.

Here is what to do, in order.

Step 1: identify the plugin

If the problem started right after a plugin update, that plugin is the likely cause. WordPress often emails the site admin a recovery mode link naming the plugin that caused a fatal error. Check that email first.

Step 2: deactivate it

• If you can log in: go to Plugins and deactivate it.
• If you use recovery mode: follow the email link and deactivate it there.
• If you cannot log in: use the host’s file manager or SFTP, open wp-content/plugins and rename the plugin’s folder.

Step 3: roll back or restore

The WP Rollback plugin can install a previous version of plugins from WordPress.org. Restoring from a backup is safer when you are unsure what changed.

Step 4: find out why

Check the PHP error log or enable debugging to see the exact error. The WordPress debugging guide explains how. Common causes are conflicts with another plugin or theme, an outdated PHP version or a bug in the new release.

Step 5: report it

Tell the plugin developer what happened, including your WordPress and PHP versions and the error message. Popular plugins often release a fix within days.

Example: a quick recovery

A store’s checkout stopped loading after a payment plugin update on a Friday evening. The owner received the recovery mode email, deactivated the plugin and switched customers to a second gateway that was already set up. The next morning, the maintenance team rolled the plugin back to the previous version on staging, confirmed it worked and applied it live. The developer released a fix the following week. Downtime was limited to minutes, because the owner had a backup gateway and a clear process for a bad plugin update.

How to prevent problems with a plugin update

1. Take a backup before every update.
2. Test updates on a staging site first, especially for stores.
3. Update one plugin at a time so you know which one caused a problem.
4. Avoid updating major plugins right before busy periods.
5. Remove plugins you no longer need.
6. Read changelogs for major version updates.

Should I turn off automatic updates?

Automatic updates keep sites secure, especially for minor and security releases. For critical plugins on stores, many teams prefer manual updates after testing. A mix works well: automatic for small plugins, tested manual updates for checkout, membership and page builder plugins.