All articles

How to Update WordPress Safely Without Breaking Your Site

By Deeb Chreif3 min read

WordPress, theme and plugin updates keep your site secure, but can break it. A step-by-step routine to update safely, and what to do if something breaks.

WordPress runs a large share of business websites, and its plugins are a big part of why. They are also the most common way into a site for attackers: an outdated plugin with a known security hole is an open door.

So updates are not optional. But an update can also break a layout, a form or a checkout. The answer is not to stop updating, but to update with a routine. WordPress's own guide to updating covers the basics; this article adds the routine around it.

Why updates matter

  • Security: most updates fix vulnerabilities that are already public, which means attackers know about them too
  • Compatibility: plugins, themes and PHP versions move together, and falling far behind makes the next update harder
  • Speed and features: updates often make the site faster and fix bugs

The longer a site goes without updates, the riskier the eventual update becomes.

Before you update

  1. Take a full backup of the files and the database, and store it off the server
  2. Read the changelog of major updates, especially for your theme, page builder and store plugins
  3. Check compatibility: does the plugin support your version of WordPress and PHP?
  4. Choose a quiet time, not just before a campaign or a busy sales day

Use a staging copy

A staging site is a private copy of your website where you can test changes. Many hosts create one in a few clicks.

Update everything on staging first, then click through the pages that matter: the home page, a few inner pages, every form, and the full checkout or booking flow. If everything works, repeat the updates on the live site.

Update in the right order

  1. WordPress core
  2. Plugins, one at a time for the important ones
  3. The theme
  4. PHP, when your host offers a newer version and your plugins support it

Updating one thing at a time makes it easy to see which update caused a problem.

If something breaks

  • Stay calm and note what changed: which update, and what stopped working
  • Roll back the plugin to its previous version, or restore the backup you took
  • Check for a fix: the plugin's support page often reports the same problem within hours
  • Do not keep a vulnerable version for long: replace the plugin if it is no longer maintained

Reduce what needs updating

Every plugin you remove is one less thing to update and one less way in. Delete plugins and themes you do not use, avoid plugins that have not been updated in a long time, and prefer one solid plugin over three small ones.

Should automatic updates be on?

Automatic updates for small security releases of WordPress core are sensible for most sites. For major updates, page builders and store plugins, automatic updates can break things while nobody is watching. Many sites do best with automatic minor updates and a monthly, tested routine for the rest.

When to hand it over

If your site earns enquiries or sales, updates deserve a routine and someone responsible for it. That is the core of a maintenance plan. See why choose KamiKode for website maintenance for how we handle it.

Updated: