Active incident or hacked WordPress? Ransomware Hacked WordPress 423-888-0252 · 828-484-1257

Updates · what to do before you roll back

A WordPress update broke my site: what to do before you roll back

You clicked Update, and the site went white, the layout broke, or the dashboard will not load. The first instinct is to restore last night's backup or roll the whole site back. Pause. Take a copy first, then find which update caused it. Rolling the entire site back can hide the real cause, or undo work that was not the problem.

Avery Parker · principal Support since the early 1990s Networks & security since the late 1990s Linux since ~2000 Johnson City office · you talk to the same person

1. Take a copy first

Before you change anything else, make a copy of the files and the database, or a host snapshot if you have one. That copy is your evidence and your way back if the next step does not help.

Do not overwrite the live site with a backup until you know what broke. A full restore can bury the error, mix an older infection back in, or throw away recent posts and orders. The same idea is in why not to wipe the host first. If you are not sure the backup itself is usable, see how to tell if a backup would actually restore.

2. Find which plugin or theme update did it

A break that starts in the same minute as an update is usually that update, or a conflict with something already on the site.

  • Check what just changed: WordPress updates, plugin and theme pages, host or auto-update emails, and any recovery-mode message WordPress sent.
  • If several items updated at once, test one at a time on the copy, not on the live site.
  • A plugin or theme conflict often shows as a white screen, a PHP error, a missing layout, or a dashboard that will not load. That is different from spam titles, a new administrator, or a redirect you did not add.

Write down the name and version that changed, and the time. That short record saves a lot of guessing later.

3. Roll back that one component, not the whole site

If a plugin update broke the site, restore the previous version of that plugin from the copy you just made. Do the same for a theme. Leave the rest of the site alone.

Do not install an older zip from an unofficial site. Use your own copy or a version you already had. Leaving an outdated plugin or theme in place is a temporary step so the site works; plan a proper fix next (a compatible replacement, a patch from the developer, or a careful update on a copy first).

A WordPress core update is harder to isolate. You may still need a fuller restore, but start with a copy and a diagnosis, not a wipe. After the site loads again, look at hardening vs a Care plan so the next update is not another emergency.

4. How to tell a bad update from a hack

A bad update usually starts right after you, your host, or an auto-updater applied a change. You see a white screen, a PHP error, a broken theme, or a plugin that will not load. You do not see new administrator accounts, spam pages, unexpected redirects, or files you did not add.

A hack can show up around the same time as an update, especially if an outdated plugin was already open to abuse, or if an unofficial package was installed. Warning signs include a new administrator, spam in search results, phone visitors sent somewhere else, or mail going out that you did not send.

If it looks like a hack, do not treat a rollback as the cleanup. Start with the first 24 hours and the compromise checklist, and book a cleanup if you need one. Cleanup packages start around $2,500 on the incident response page.

Keeping updates from becoming emergencies

Updates are safer when they run on a schedule, on a copy first when the change is large, and with a check afterward that the site still loads, forms still send, and checkout still works if you have one. Our WordPress Care plans are $149 / $249 / $399 a month depending on tier, and they include that kind of upkeep.

Nothing here is a promise that an update will never break a site. It is a way to keep a break small and reversible.

Work with us

Work is remote nationwide; Tri-Cities and Western NC onsite is by appointment. Call TN 423-888-0252 or NC 828-484-1257.

Want updates handled vs think it was hacked

Want updates handled with a check afterward

Plugins, themes, and WordPress core on a regular update schedule, with a check that the site still loads. $149 / $249 / $399 a month.

WordPress Care plans

TN 423-888-0252 · NC 828-484-1257

This does not look like a bad update, or you think the site was hacked

Published cleanup packages with a written report. A rollback is not the cleanup if the site was compromised.

WordPress incident response

First day and want to move carefully

Download the printable first-24-hours compromise checklist. Evidence, access hygiene, and stop-lines. Not a full clean by itself.

Get the free checklist

Before you roll back questions

Should I restore the whole site from last night's backup?

Not first. Take a copy, find which update broke, and roll back that plugin or theme if you can. A full restore is a later option, not the first move.

The site is a white screen. How do I see what failed?

Use the copy and any recovery-mode or error email WordPress or the host sent. If you turn on debugging, do it briefly and not in a way the public can see, then turn it off.

Is a broken update the same as a hack?

No. A bad update usually stops the site from loading or laying out correctly, right after the change. A hack often adds users, spam, redirects, or files you did not put there. When those signs are present, treat it as an incident, not just a rollback.

Can I leave the old plugin version in place?

Only as a short pause so the site works. Plan a fix, because an old version can be the next way in.

Want updates handled with a check afterward? See WordPress Care plans.

Tri-Cities 423-888-0252 · Western NC 828-484-1257