In short: If a plugin update took your site down, rename the plugin folder under wp-content/plugins and WordPress will deactivate it. Put the previous version back from wordpress.org or with WP-CLI. If the update also changed the database, restore from a backup instead.
A white screen after an update, or the message "There has been a critical error on this website". This is what people contact me about most often. Usually a single plugin update broke the site, and it can be back within fifteen minutes. This article is for the case when you cannot even get into wp-admin. The general steps are in the article on a site broken after an update, and what the common error messages mean is in this one.
1. Which plugin update broke the site?
- Check your email. On a critical error, WordPress sends an email to the admin address. It names the plugin that caused the error and includes a link to recovery mode, which lets you log in with the broken plugin paused.
- Check the error log. In your host's
error_logfile or inwp-content/debug.log, the path in the error line shows the plugin:wp-content/plugins/plugin-name/.... - If there is no log, turn it on in
wp-config.php:define( 'WP_DEBUG', true );,define( 'WP_DEBUG_LOG', true );anddefine( 'WP_DEBUG_DISPLAY', false );. Turn it off again once fixed.
If you updated several plugins at once, there are more suspects. Disable them one at a time.
2. Disable it without wp-admin
Open your host's file manager or connect over FTP, and in wp-content/plugins rename the plugin's folder, for example from woocommerce to woocommerce-off. WordPress can no longer find the plugin and deactivates it. The site should come back.
If you have SSH access and WP-CLI: wp plugin deactivate plugin-name --skip-plugins. You need --skip-plugins because the broken plugin would crash WP-CLI as well.
3. Put the old version back
For a free plugin from wordpress.org, open the plugin page, click Advanced View, and download the previous release from the Previous versions list at the bottom. Upload the contents of the zip to wp-content/plugins and delete the old renamed folder.
With WP-CLI it is one line: wp plugin install plugin-name --version=1.2.3 --force. The details are in the WP-CLI documentation.
For a premium plugin, download the older version from your account with the vendor. Elementor also has its own rollback under Tools → Version Control.
4. Watch out for the database
Some plugins change the database when they update. WooCommerce, for example, asks for a separate database update. In that case the old version does not always work with the new database. If odd errors appear after the rollback (missing orders, empty settings), the reliable route is restoring the backup taken before the update, files and database together.
5. Turn off auto-updates for that plugin
Otherwise WordPress will reinstall the broken version within hours. On the Plugins page, disable auto-updates in the plugin's row, or with WP-CLI: wp plugin auto-updates disable plugin-name. Check the plugin's support forum too. If others report the same problem, that is usually where you find out when the fixed version is coming.
How to prevent it
- Always have a fresh backup of files and database before updating.
- Do not update twenty plugins at once, because afterwards it is hard to tell which one caused the error.
- Try big updates (WooCommerce, Elementor, page builders) on a copy of the site first.
If your site is down right now and you do not know which plugin is to blame, write to me. With monthly maintenance I test updates on a copy before they reach the live site.
