Blog / How the internet works /

Keeping plugins, themes and core updated safely

There are two ways to get WordPress updates wrong. One is never updating, so the site slowly becomes a museum of known security holes. The other is clicking “update all” at 5pm on a Friday and hoping.

Both are common. Neither is a plan.

The middle route is boring and works: update regularly, in a sensible order, with a way back. Here’s a method that suits a small site, and how it scales if you look after several.

Why updating matters at all

Updates do three jobs: they fix security problems, they fix bugs, and they keep software compatible with the rest of the stack (PHP, other plugins, WordPress itself). Skipping them doesn’t preserve a working site. It postpones the breakage and adds risk while you wait.

Most hacked WordPress sites aren’t victims of clever attacks. They’re running something old, with a flaw that’s publicly documented. That’s why the sensible default is: keep things current, but never without a safety net.

Step 1: have a backup you trust

Before any update, you need a fresh backup of both files and database. Not “I think the host does one”. A backup you know exists and have seen work.

If you’ve never restored one, do a practice run first. I wrote about the setup in WordPress backups: a setup that saves you on the worst day and about rehearsing the restore in restoring a website from backup: a practice run. If your site takes orders or user data, take a database backup right before updating too, as covered in WooCommerce and WordPress database backups before plugin changes.

Step 2: look before you leap

Don’t update blindly. For each pending update, spend a minute checking:

  • What kind of update is it? Patch versions (1.2.3 to 1.2.4) are usually small fixes. Minor versions (1.2 to 1.3) add features. Major versions (1.x to 2.0) can change a lot.
  • Is it marked as a security fix? If yes, move it up the queue.
  • What does the changelog say? You’re looking for words like “breaking change”, “requires PHP 8”, “database update”.
  • Does it say it’s tested with your WordPress version?
  • Is the plugin still maintained? One that hasn’t been updated in years is a risk in itself.

Step 3: use the right order

A sensible order reduces surprises:

  1. WordPress core, particularly when a plugin needs a newer version.
  2. Plugins, starting with the least critical.
  3. Theme, after confirming whether you’ve changed theme files directly (more below).
  4. Translations and minor extras, last.

Update one thing at a time when you can, or small batches of related items. If something breaks after ten simultaneous updates, you’ve got ten suspects. After one, you have one.

Step 4: test on staging when it matters

A staging site is a private copy of your website where you can break things safely. Many hosts include one. For a simple brochure site, you might not need it. For a shop, a membership site or anything with forms and payments, it’s worth the effort.

Update on staging first, then check the important paths:

  • Homepage and a couple of key pages
  • Contact form submission
  • Checkout or booking flow
  • Login
  • Anything the plugin you updated touches

Only then repeat the updates on the live site. WordPress plugin update planning for WooCommerce sites goes through this for shops.

Step 5: choose your timing

  • Avoid peak times. Don’t update a shop on the morning of a sale.
  • Avoid Friday evening unless it’s a security emergency. Problems need someone to fix them.
  • Keep an eye on the site afterwards. Check it again after a few hours, not just straight after.

Step 6: verify after each update

After updating, don’t just load the homepage. Walk through what matters:

  • Does the front end look right on mobile and desktop?
  • Do forms send, and do the emails arrive?
  • Are there any PHP errors or white screens?
  • Is the page speed in the same ballpark?
  • Does the admin area still load properly?

A quick uptime monitor with a keyword check helps catch the quiet failures, such as a page that loads but shows an error message.

Step 7: know how to roll back

If an update breaks something, you have three options:

  • Roll back just the plugin. Some tools let you reinstall a previous version. You can also upload the old version manually via FTP or your file manager.
  • Restore from backup. The nuclear option, so make sure it’s recent.
  • Disable the plugin temporarily. If you can’t get into the admin, rename the plugin’s folder via FTP or the file manager. WordPress will deactivate it.

Write the steps down before you need them. Panic is a bad time to learn where the plugins folder is.

The theme trap

Updating a theme can wipe out changes you made directly in its files. If you’ve edited theme files, an update will overwrite them.

The fix is a child theme, which holds your customisations separately, or moving custom code into a small plugin. If someone else built the site, ask whether a child theme is in use before updating. This is also why the handover list in website accounts to hand over when a developer leaves includes custom code.

Automatic updates: yes, with limits

WordPress can update automatically, and it’s worth using for:

  • Minor core releases, which are mostly security patches, are on by default.
  • Small, well-maintained plugins that are low-risk.

I’d be more cautious about automatic updates for page builders, WooCommerce, membership plugins or anything touching checkout. Those deserve a human look first. Some people use automatic updates for everything and are fine, but they pair it with solid backups and monitoring. If you go that route, don’t skip the safety net.

If you manage many sites

The principle is the same, with more structure: a schedule, a log of what changed, and a standard test list. Managing plugin updates across many WordPress sites covers that, and update day: how I plan website updates looks at the planning side.

Pre-update checklist

  • Fresh backup (files and database) that you know can be restored
  • Changelog read, especially for major versions
  • Order planned: core, plugins, theme
  • Staging tested if the site is critical
  • Quiet time chosen
  • Rollback steps written down
  • Post-update checks ready

Key takeaways

  • Updating is safer than not updating, if you have a backup and a plan.
  • Read changelogs, update in order, and change one thing at a time.
  • Test critical sites on staging.
  • Know how to roll back before something breaks.
  • Use a child theme so updates don’t erase your changes.

Pick one site you look after and write down its rollback steps today, even in three lines. Next time an update goes wrong, you’ll thank yourself.