What this problem looks like
The WordPress dashboard makes bulk updates tempting. On a live shop or membership site, bulk updates hide which plugin broke checkout or login. A safe update routine treats each plugin as a small deployment with a backup and a quick test pass.
Staging copies, maintenance mode, and WP-CLI give you faster rollback than guessing which of twelve plugins failed. The steps below work whether you manage one site or twenty client sites.
Prepare before you click Update
Open your hosting panel and confirm you have a backup from today or create one with your backup plugin, host snapshot tool, or a manual export.
Note your active theme, PHP version, and any plugins tied to payments or membership. Those deserve extra caution or a staging test first.
- Export or snapshot the database.
- Download wp-content/plugins via SFTP if you lack automated backups.
- Disable auto-updates on WooCommerce, membership, and page builder plugins until tested.
Update from wp-admin
Log in as an administrator and go to Dashboard → Updates or Plugins → Installed Plugins.
Update one plugin, then load the front end and wp-admin in a private browser window before continuing.
- Click Update Now on a single plugin.
- Wait for the success message.
- Test homepage, one inner page, and any form or cart flow.
- Repeat for the next plugin.
Update with WP-CLI on SSH
Servers with SSH and WP-CLI let you update from the command line and script the process for multiple sites.
cd /path/to/wordpress
wp plugin list --update=available
wp plugin update contact-form-7
wp plugin update woocommerce --version=8.6.1Use staging for risky plugins
Page builders, SEO suites, and custom CRM connectors often break layouts after updates. Clone the site to staging, run the update there, and click through real content before touching production.
If staging is not available, schedule updates during low traffic and keep FTP access open so you can rename a plugin folder quickly.
When an update breaks the site
If wp-admin dies after an update, rename the plugin folder via SFTP or restore the plugin folder from backup. See our rollback tutorial for version-specific recovery.
Leave the plugin deactivated until the vendor ships a fix or you can test on staging.
When to stop DIY and hire help
If plugin updates keep breaking production and you cannot maintain staging, BugShield offers fixed-price plugin conflict fixes from £49.99 with a BugShield developer and secure Vault access for wp-admin and hosting.