Emergency repair

A WordPress update broke your site.

Usually recoverable, and usually quickly — provided nobody makes it worse in the first ten minutes by trying things at random on the live site.

Same-day in working hours Cause found Prevented next time
Right now

The first ten minutes matter.

If the site is down or broken after an update, the most useful thing is to stop changing things. Updating other plugins to see if it helps, deleting files, or reinstalling on top tends to turn a one-hour fix into a restore from backup.

What actually helps: note exactly what was updated and when, and check whether a backup from before it exists. Those two facts determine whether this is a quick reversal or a longer diagnosis, and they are easy to lose if people start experimenting.

The underlying cause is nearly always a conflict rather than the update itself being faulty — a plugin relying on something the new version changed, a theme calling a function that was removed, or two plugins that both worked until one moved.

Able Web Services Ltd.UK web development
200+PROJECTS DELIVERED
140+CLIENTS SUPPORTED
15+YEARS ESTABLISHED
UKBASED & HOSTED

What we do

  • Bespoke websites and custom CMS development
  • Ecommerce, custom checkout and subscriptions
  • Web applications, portals and internal tools
  • API, CRM and business systems integration
  • Retained support, maintenance and managed hosting
  • White-label development for agencies

Working UK-wide — directly with businesses, and white label behind design and marketing agencies.

Discuss a project
How it gets fixed

The sequence that works.

Get it back first

Restore or revert so the site is serving again. Diagnosis happens on a copy, not on the thing your customers are looking at.

See the actual error

A white screen is not the error. Enabling proper logging turns guesswork into a specific file and line.

Isolate the conflict

On a copy, not live. Usually quick once the error is visible, because the error names the culprit.

Fix rather than pin

Holding a plugin on an old version works today and becomes a security problem later. Fixing the conflict is the real answer.

Re-apply safely

The update tested on staging first, so the same thing does not happen twice in a week.

Stop the repeat

Staging, backups and a tested update process. This is what the monthly care hour is for.

Straight answers

Worth saying plainly.

Updating straight to live is the real cause

Not the update. If changes go to production untested, this will happen again regardless of who fixes it this time.

No backup makes it harder, not hopeless

There is usually still a route. It takes longer and the diagnosis matters more, and the backup position is the first thing we check.

Not updating is worse

Sites broken by updates sometimes stop updating entirely. That trades a visible problem for an invisible one, and the invisible one is a compromise.

Related services

The wider picture.

Related work

Projects of a similar shape.

A lot of our work is delivered white label or under agreement, so these describe the problem and the approach rather than naming the client.

Questions

What people ask when an update breaks things.

Can you fix it today?
Usually, in working hours. Our coverage is Monday to Friday, 8am to 6pm, and our response target for a site that is offline or unusable is 2 business hours. Phone rather than email if it is urgent.
We have no backup. Is it recoverable?
Often. Many update failures are a conflict that can be identified from the error and resolved directly. A backup makes it faster and lower-risk, which is exactly why we check for one first.
Should we just turn updates off?
No. Unpatched WordPress sites get compromised, and that is a worse day than this one. The answer is testing updates before they reach the live site, not avoiding them.
Why did it work for everyone else?
Because the problem is usually a conflict particular to your combination of theme and plugins rather than the update being broken. That is also why testing on a copy of your site catches it when general testing does not.
Next step

Tell us what you updated and when.

Those two facts get us most of the way to the cause. If the site is down right now, call rather than email — and try not to change anything else in the meantime.