•

My WordPress site broke after an update: how to roll it back safely

Updates are meant to be routine, and most of the time they are. When one goes wrong, the temptation is to start undoing things in a hurry: switching plugins off at random, restoring last week’s backup, or updating everything else in the hope it sorts itself out. Each of those can make things worse. The calmer route is to work out exactly what changed, and put back only that.

Is this what you’re seeing?

  • Your WordPress website stopped working straight after you clicked Update, or after an update ran on its own overnight.
  • The site broke after updating one plugin, and now shows a critical error, a blank page or a broken layout.
  • You updated Elementor and now the site, the editor, a form or a popup doesn’t work.
  • The shop broke after updating WooCommerce: products, the basket or the checkout misbehave.
  • The theme broke after an update, or your changes to it have disappeared.
  • You need to roll back a plugin update safely, but you don’t know which version to go back to.

What usually causes it

One plugin that no longer suits the rest of the site

The most common cause. A plugin is updated and now clashes with another plugin, with your theme, or with your version of WordPress or PHP. The update itself is usually fine on other sites. It’s the combination on yours that fails. How to tell: the site broke right after a particular update, and the error message or WordPress’s “technical issue” email names a folder in wp-content/plugins/. If there’s a fatal error, my guide to “There has been a critical error on this website” covers finding it.

A free plugin and its Pro add-on out of step

Elementor and Elementor Pro, WooCommerce and its paid extensions, and many form and SEO plugins come in pairs. The free half often updates from wordpress.org, while the Pro half updates from the vendor and needs a valid licence. If one moves and the other doesn’t, they can stop working together. How to tell: compare the two version numbers on the Plugins screen. A big gap between them, or a notice asking you to update the Pro version, points here. I cover this in more detail in Elementor and Elementor Pro out of step after an update.

WooCommerce moving ahead of its extensions or your theme

WooCommerce updates often, and your payment gateway, shipping plugin and theme have to keep up. Themes that change WooCommerce’s own page templates can fall behind, and an older payment plugin can stop the checkout taking payments. How to tell: in WooCommerce → Status, scroll to the template section. Outdated template copies in your theme are flagged there. If payments stopped, check whether the payment plugin itself has an update or a notice asking you to reconnect your account.

A theme update that replaced your changes

If someone edited the theme’s own files, for example its stylesheet or functions.php, those edits are overwritten when the theme updates. Changes made in a child theme, or in the Customizer or Site Editor, survive. How to tell: the layout or colours went back to how the theme looks out of the box, or a feature that was added by code has vanished.

Old cached files after the update

After an update, a caching plugin or a page builder can carry on serving CSS and JavaScript built for the old version. The page looks broken even though nothing is actually wrong with the new version. How to tell: the layout is broken, but there’s no error, and it looks different in a private window or on another device.

An update that didn’t finish

If the connection drops or the server times out mid-update, a plugin can be left half old and half new, or the whole site stuck on “Briefly unavailable for scheduled maintenance”. How to tell: you see that maintenance message, or an error says a file “failed to open”. See stuck in maintenance mode.

What you can safely try

Take a backup first, of the broken site as it is now. If something goes wrong while you’re rolling back, you want to be able to get back to this point. If you can’t log in, take it through your host’s control panel, or ask your host to.

  1. Work out what changed. If you clicked Update yourself, you’ll know. If it happened overnight, look at the dates on the folders in wp-content/plugins/ and wp-content/themes/ in your host’s file manager. Folders that changed when nobody was working on the site are the first suspects.
  2. Clear every cache: your caching plugin, your host’s cache and Cloudflare if you use it. If the site is built with Elementor, its Tools screen has an option to regenerate its CSS files. Then check in a private window.
  3. Deactivate the plugin you suspect, from the Plugins screen, and check the site again. Don’t delete it: deleting can remove its settings too. If you can’t get into wp-admin, rename its folder in wp-content/plugins/, for example from plugin-name to plugin-name-off. Rename it back to undo.
  4. If that plugin is one you need, roll it back to the version you had. For free plugins from wordpress.org, the plugin’s page there keeps previous versions (look for “Advanced View”), and the free WP Rollback plugin can do it from your dashboard. For Pro plugins, download the older version from your account with the vendor. Elementor has a version rollback option on its own Tools screen.
  5. To install an older version from a zip file, go to Plugins → Add New Plugin → Upload Plugin and choose the file. WordPress will offer to replace the current version with the uploaded one. Your settings stay in place.
  6. Once the site works, turn off auto-updates for that one plugin on the Plugins screen, so it doesn’t update itself again tonight. Make a note to update it properly once the clash is sorted.

When to stop and get help

  • It was WooCommerce, a membership plugin or WordPress itself that updated. These can update your database as well as their files, and putting the old files back over a newer database can do more harm than the original problem.
  • The shop has stopped taking payments, or bookings and member logins aren’t working. Every hour matters, and recent orders need checking.
  • Rolling back one plugin breaks another, and you’re going round in circles.
  • You don’t know which version worked, or the Pro version needs a licence you don’t have.
  • Someone suggests restoring a backup over the live site. That throws away every order, enquiry and edit made since the backup was taken.
  • It keeps happening every time you update. That’s a sign the site needs a proper look, not another rollback.

A real example

A London restaurant’s site, built with Elementor, broke during maintenance and hosting work because Elementor and Elementor Pro had ended up on versions that didn’t work together. The contact form and the popup menu stopped working along with it. Updating everything to the newest versions wasn’t the safe answer. I found a pair of versions that worked with each other and with the rest of the site, and put those back, which brought the form and the popup menu back to a working state. The full story, and how to find a stable pair yourself, is in my Elementor guide.

The lesson I take into every rollback is the same: go back one step, to a combination you know worked, rather than forward into the unknown. Then update properly, on a copy of the site, once it’s stable.

Getting it fixed

Tell me what updated and when, if you know, and send a screenshot of what you’re seeing. I take a full backup, find the update behind it, roll back or fix only what’s needed, and check the parts that matter to you, such as forms and the checkout. A WordPress repair is a fixed £119, which covers finding the problem and up to 90 minutes of fixing it. Most repairs fit in that, and you’re never charged more without agreeing first.

If your site is down and it’s costing you money right now, see emergency WordPress support for a faster start.

Questions

My site breaks whenever I update plugins. What am I doing wrong?

Probably nothing, except updating everything at once on the live site. When ten plugins update together and something breaks, you can’t tell which one did it. Update one at a time, check the site after each, and test big updates on a staging copy first. If that’s more than you have time for, a care plan does it for you, and I fix anything my updates break at no extra cost.

My WooCommerce store stopped accepting payments after an update. What should I check?

Check the payment plugin first: whether it needs its own update, and whether it’s showing a notice about reconnecting your Stripe or PayPal account. Then place a small test order yourself. If the payment methods have disappeared from the checkout, see Stripe or PayPal stopped working. Don’t roll back WooCommerce itself without a backup and a plan.

I updated Elementor and now my site doesn’t work. Should I update Elementor Pro too?

Often, yes: the two need to be on versions that work together, and the Pro update may simply be waiting for a licence check. If updating Pro isn’t possible, or doesn’t help, rolling the free Elementor back to the version you had is usually the quicker way back to a working site.

My theme update removed my customisations. Can I get them back?

If you have a backup from before the update, the old theme files are in it, and the changes can be copied out and moved into a child theme so the next update doesn’t wipe them. Don’t restore the whole backup over the live site to get them: just the theme files are needed.

Should I just turn off all automatic updates?

Not all of them. Security fixes matter, and a site that’s never updated becomes harder and riskier to update later. Turning off auto-updates for the one or two plugins that have caused trouble, and updating those by hand, is a sensible middle way. Some hosts also run their own updater, which is worth knowing about: see why your host’s auto-updates can break your site.

Written by Peter Claridge, who fixes WordPress sites for businesses across the UK from Reading. Last checked on WordPress 7.1, November 2026.