The Site Broke After an Update: Read This Before Rolling Back

The panel showed "updates available", you clicked. The page reloaded and the layout fell apart. Or the site will not load at all. Or everything looks fine but the contact form no longer works — which is the most dangerous outcome, because nobody notices for weeks.

First, know this: it is not bad luck. An update means the code changed, and any change made without testing has some chance of breaking things. The question is not "why did it break" but "why was it done untested".

What to Do Immediately

1. Do not panic-rollback

The first instinct is to undo everything. But a rollback performed without knowing what broke can also revert the database, losing the orders, form submissions and comments that arrived in between. Identify what broke first.

2. What exactly is broken?

• Site will not load at all: probably a fatal error — follow the white screen or 500 error path.
• Layout fell apart: a version mismatch between theme and plugins, or a cache serving old files.
• One function stopped working (form, payment, search, filters): most likely the plugin providing it.
• Admin loads but the front end is broken: look at the theme.

3. Clear the cache — try this first

A surprising share of "the update broke it" cases are cache problems: browser and server keep serving old files that now mix with new code. Clearing caches takes minutes and resolves a meaningful portion of incidents.

4. Roll back the last thing updated, not everything

Rather than reverting every update, identify the component updated last and revert only that. You keep the security patches the other updates brought.

Why It Breaks: Four Typical Causes

Inter-plugin dependencies. One plugin uses a function another provides; the provider updates and changes it, and the consumer breaks.

Theme customisations overwritten. If theme files were edited directly, a theme update erases those edits. The correct method is a child theme; otherwise every update keeps deleting your work.

PHP version mismatch. The new version does not run on the old PHP, or the reverse. Our PHP errors article covers exactly what breaks.

Database schema changes. On major version jumps, plugins migrate their own tables. If that migration halts halfway, data becomes inconsistent — the hardest scenario to roll back.

The Permanent Fix: How to Update Properly

1. Take a backup — files and database together.
2. Apply it on a copy that mirrors production.
3. Exercise the critical flows: submit a form, run a payment step, search, log in, check mobile. The list is short but it should be written down.
4. Check the error log. Even if the screen looks fine, new errors in the log mean the update is not clean.
5. Go live and test again. What worked on the copy may not work in production; environments differ.

This takes half an hour per update. Fixing a broken site takes a day — during which the site sells nothing.

Should Automatic Updates Stay On?

Yes for security patches, no for major version jumps. Auto-applying small security releases reduces risk; major upgrades need to be controlled. Turning everything to automatic without that distinction means your site can break while you sleep.

When You Need a Professional

Stop if a database migration halted midway, if the order flow on an e-commerce site is affected, or if a rollback did not restore the site. Beyond that point every attempt raises the risk of data loss. We always resolve this on a copy and apply only a verified fix to production.

A Pre-Update Checklist

1. Is there a backup? Files and database together — and has it been verified to restore?
2. Have you read the release notes? On major versions, developers usually document what changed. Five minutes of reading beats hours of searching.
3. Is the critical flow list ready? What absolutely must work on this site — form, payment, search, login, filters? Write it down.
4. Is the timing right? Do not update on a Friday evening. Never make changes in a window where nobody is around to fix the fallout.
5. What is the rollback plan? Knowing in advance what you will do if it breaks prevents panic decisions.

One at a Time or All at Once?

The "update all" button is tempting and expensive diagnostically. Update ten plugins together, break the site, and you now have to revert them one by one to find the culprit.

Our balanced approach: batch the small security updates, do major versions one at a time, exercising the critical flows after each. It turns a ten-minute job into twenty and saves hours when something breaks.

Order matters too: core first, then the theme, plugins last. Done in reverse you can install a plugin version incompatible with a core you have not upgraded yet. It looks like a detail and it matters in practice.

What Would It Cost If We Fixed It?

You do not have to guess, and you do not have to ask us. Tick the items you need in the calculator on our site and the total appears instantly. No forms, no waiting for a quote.

Calculate your price in one minute →