Get an estimate
WordPress

Why WordPress websites break after updates, and how to prevent it

Plenty of WordPress updates go through without anyone noticing. The ones that don't tend to fail for a handful of predictable reasons, and nearly all of them can be caught on a copy of the site before they ever reach the real one.

Oogle Published 6 minute read
Illustration of two identical outlined browser windows side by side, the left one marked as a copy, with a circular update arrow lit in blue between them, on dark navy.

WordPress sites usually break after updates for a handful of reasons: two plugins that stop working together, a theme with out-of-date copies of plugin templates, a PHP version change, a database update cut off partway, an abandoned plugin, edits made inside plugin files, or a stale cache. Testing each update on a copy of the site first catches nearly all of them.

Updates aren't optional. They fix security holes, keep WordPress compatible with newer versions of PHP, and keep plugins working with each other. Putting them off doesn't make a site safer; it makes each update bigger, and a site that jumps several versions at once is harder to update cleanly.

But every update changes code your site depends on, so it's also one of the moments a working site is most likely to break. Knowing why that happens makes it much easier to prevent.

What an update actually changes

A WordPress site is several pieces of software made by different people: WordPress itself, a theme, a collection of plugins, and the PHP version on the server that runs all of it. Each piece updates on its own schedule. An update to one piece is tested by its developer, but nobody else has your exact combination of the others. That combination is where most breakage happens.

The usual reasons an update breaks a site

Two plugins that disagree. Each works fine alone. After one of them updates, they load the same library in different versions, hook into the same moment in different ways, or one starts doing something the other already did.

A theme that overrides plugin templates. Themes can replace parts of a plugin's output, which WooCommerce stores rely on heavily. When the plugin updates its templates and the theme's copies stay old, pages can break or quietly lose features. WooCommerce lists out-of-date template overrides on its status screen for exactly this reason.

A PHP version change. Hosts upgrade PHP because old versions stop receiving security fixes, and WordPress itself now recommends PHP 8.3 or newer. Code written for an older version can fail on a newer one, and newer plugins can require a PHP version your server doesn't have yet. WordPress won't install a plugin update that requires a newer PHP or WordPress version than your site has, as declared in the plugin's requirement headers. That prevents some of these, but it only works when the author declares it, and it does nothing about old code failing on new PHP.

A database update. Some plugins change how they store data when they update. If that step is interrupted or fails partway, the site can be left half updated.

An abandoned plugin. A plugin nobody maintains doesn't break when it updates. It breaks when everything around it does.

Edits made in the wrong place. If someone customized a plugin or theme by editing its files directly, the next update overwrites those changes without warning. Child themes and custom plugins exist so changes survive updates.

A license that lapsed. Premium plugins and themes usually need an active license to receive updates. When one lapses, that plugin quietly stops updating and falls further behind everything around it.

Caching. After an update, a cache can keep serving old stylesheets and scripts alongside new code, so pages look broken until the cache is cleared.

A change in one place can break something somewhere else

Not every problem comes from the update itself. Sometimes an update or a fix switches on something that was already there.

We saw this on our own site in September. While fixing a scheduled-task problem after a server move, a lazy-loading option in our caching plugin, which had been switched on all along but never actually running, started working for the first time. It began delaying the main image on our pages, and our pages got noticeably slower to show their first content. Our routine speed checks caught it within hours and we switched the option off. Nothing about that was in any changelog. The only way to catch it was to check the site after the change.

What WordPress does to protect you now

WordPress has added several safety nets over the years, and they're worth knowing about because they change what a failed update looks like:

  • Minor releases of WordPress itself, the ones that mostly contain security and bug fixes, install automatically by default. On sites first installed since WordPress 5.6, in late 2020, major releases are set to update automatically too, unless a host or developer changed that.
  • You can turn on automatic updates for plugins and themes. They're off by default, apart from rare forced security updates from WordPress.org.
  • If an automatic plugin update causes a fatal error, WordPress rolls it back to the previous version and emails the admin. The check is narrow, though: it loads only the home page, looks only for a crash, and doesn't cover themes or updates you run by hand.
  • When a plugin or theme causes a fatal error, WordPress shows the critical error message and emails the site's admin address a recovery link, as long as the site can send email. Logging in through that link pauses the plugin or theme for you, so you can deactivate it. Visitors still see the error until you do. Our guide to the critical error message walks through it.

These help a lot with crashes. None of them can tell whether your checkout still takes payments, your booking calendar shows the right dates, or your quote form still sends. A site can be fully up and quietly broken.

How to update without breaking things

The routine that prevents most update problems isn't complicated. It just has to happen every time:

  1. Take a backup immediately before updating, separate from the scheduled one, so you can get back to the minute before the change.
  2. Apply the updates to a copy of the site first, often called a staging site. Many hosts can create one with a click.
  3. Check the copy the way a customer would: submit the forms, run a test purchase or booking, log in, and look at the pages that bring in work. Check the error log for new warnings.
  4. Then apply the same updates to the live site, ideally at a quiet time, and check the same things again.
  5. Update one major component at a time on the live site, so if something breaks you know which change did it.

On a store, there's one extra rule: never copy a staging site back over a live store's database. Orders and customer accounts keep arriving on the live site, and pushing the copy back would erase them. Test on the copy, then repeat the updates on the live site. WooCommerce's own update guidance says the same about backups and staging, and notes that some WooCommerce updates also need a database update once the files have changed.

Under our Website Care plan, routine updates are applied to the live site and the site is checked straight afterward, rather than tried on a separate copy first. Redesigns, rebuilds and migrations are built on a staging copy.

Write the policy down

Whoever looks after the site should be able to say, in a few lines, what updates automatically, what waits to be tested on a copy, who decides, and how quickly security updates go out. If nobody can, updates are probably happening by habit, or not at all.

Should you turn on automatic updates?

For a simple site with a few popular, well-maintained plugins, automatic updates are a reasonable choice, and they're far better than updates that never happen. For a store, a booking site, or anything with heavy customization, automatic updates for the big components are a gamble, because nobody is checking the result. A middle path is to let small, low-risk plugins update automatically and handle the large ones by hand, on a copy first.

If an update has already broken your site

Don't restore an old backup over the whole site, especially a store, without thinking about the orders and form entries that arrived since. Don't delete plugins to see what happens. Check the admin email for WordPress's recovery link, look at what was updated most recently, and roll back that one component if you can. If the screen shows the critical error message, start with that guide. If it's a store or you're not sure what changed, that's the point to get help, before anything else is changed.

Something broken, or something to build?

Describe what's going on in your own words. We'll tell you what we think and what it would take.

Get website help