How to update WordPress plugins without breaking your site

A backup, a staging copy, one update at a time, and a check of the pages that matter. The routine that keeps WordPress updates from taking your site down.

2 min read

Out-of-date plugins are how most WordPress sites get hacked. Updating them blindly is how most WordPress sites break. You don’t have to pick one risk: a short routine keeps updates safe.

Before you update

Take a backup you know you can restore. Your host’s or plugin’s backup should hold the files and the database, and live somewhere other than the server it backs up. If you’ve never restored one, you don’t yet know it works.

Read the changelog for big jumps. A move from version 4 to 5 of a plugin can change settings or drop features. WooCommerce, page builders and membership plugins deserve a look before you update.

Check your PHP version. New plugin versions sometimes need a newer PHP than your host runs. Tools → Site Health in the admin shows which one you’re on.

Update on a copy first

Most hosts offer a one-click staging copy of your site. Run the updates there first. If something breaks on staging, nothing breaks for your visitors, and you can find the cause without the pressure.

No staging? Update at your quietest time of day, and update one plugin at a time rather than all at once. When something breaks you’ll know which update did it.

Update in this order

  1. Plugins, one at a time, starting with the ones you rely on least.
  2. The theme, after the plugins. If you’ve edited the theme’s files directly instead of using a child theme, the update will overwrite those edits.
  3. WordPress core, last. Minor releases install themselves; major ones are worth the same care as a big plugin update.

Check the pages that matter

After each round of updates, open the pages that earn you money or leads, logged out and in a private window:

  • The home page and your main service or product pages
  • Every form: send yourself a test message
  • The cart and checkout, if you sell online
  • The page on a phone, not just on a laptop

If an update breaks the site

If you see “There has been a critical error on this website,” WordPress has stopped a page loading because of a fatal PHP error. Check the email WordPress sends to the admin address: it usually names the plugin or theme behind it and includes a recovery-mode link that lets you log in and deactivate it.

If you can’t get into the admin, rename the plugin’s folder in wp-content/plugins over SFTP or your host’s file manager. WordPress deactivates it, and the site should load again. Then restore from your backup, or roll back to the plugin’s previous version, and wait for a fix.

Or hand it over

Safe plugin, theme and core updates runs this whole routine on staging with a backup to roll back to. If an update has already taken the site down, fixing the critical error traces it to the plugin, theme or PHP change behind it. And if you want updates handled every month, every WP Care plan includes tested updates, with failed ones fixed by our team.

Rather we just fix it?

Find the service with its price or estimate, or book a call to talk it through.