If your WordPress site broke after an update, the reassuring news is that it is almost always fixable, and usually without losing any content. The cause is nearly always a single plugin or theme that no longer gets along with the new version of something else, and the job is to find that one piece, switch it off and get the site back up before fixing it properly.
It also tends to happen at the worst possible moment. A restaurant’s booking plugin updates itself the Saturday before Christmas, or a builder’s site goes white on the Friday evening of a bank holiday weekend, with no developer answering the phone until Tuesday.
What Should You Do First When Your WordPress Site Breaks After an Update?
Stop, before you touch anything else. Clicking every remaining update button in the hope of fixing it makes the real cause much harder to find.
Work out what is actually broken. It might be the whole site, a single page, the admin area or just the contact form, and each points somewhere different.
Look at what the screen says. A blank white page, or the message “There has been a critical error on this website”, means PHP has crashed, almost always because of a plugin or the theme.
Check the email address the site was set up with. WordPress sends the site administrator a recovery mode link when it catches a fatal error, and that link lets you log in with the faulty plugin paused. On older Irish sites that email often goes to a former employee or the original web designer, which is worth sorting out long before it matters.
How Do You Fix a WordPress Site Broken by a Plugin Update?
If the recovery email arrived, use the link, log in and deactivate the plugin it names. The rest of the site should come back straight away.
If you cannot get into the dashboard at all, you can switch the plugin off from your hosting account. Irish hosts such as Blacknight and Register365 give you a file manager in the control panel. Open the wp-content folder, then plugins, and rename the folder of the plugin that updated, adding something like “-off” to the end. WordPress can no longer find it, so it stops loading it.
Once you are back in, a rollback plugin can return the problem plugin to its previous version while you wait for its developer to release a fix.
If you cannot tell which plugin caused it, restoring the most recent backup from before the update is the quickest route back. Many shared hosting plans include backups, but not all of them keep daily copies, so it is worth checking what yours actually offers on a quiet day rather than a busy one.
What If a Theme, PHP or WordPress Core Update Broke It?
A broken theme can be switched off the same way. Rename its folder inside wp-content, then themes, and WordPress falls back to a default theme so you can log in and investigate.
A PHP upgrade is a common cause on Irish shared hosting. Hosts periodically retire older PHP versions for security reasons, and a site running plugins that have not been updated in years suddenly finds they no longer work. Most control panels let you step the PHP version back temporarily, which buys time, but the real fix is replacing the plugins that could not keep up.
When an update to WordPress itself is to blame, restoring a backup is usually the fastest answer, followed by checking which older plugins are incompatible with the new version.
Can a WordPress Update Break Your Contact Form Without You Noticing?
Yes, and this is the breakage that costs Irish businesses the most, because nobody sees it happen.
The site looks perfect. The form still sits on the contact page, and customers fill it in and press send. Behind the scenes a form plugin, a spam filter or an email-sending plugin has updated, and the enquiries are going nowhere. I have seen tradespeople lose weeks of quote requests this way before anyone noticed the phone had gone quiet.
The fix is simple and dull. After every round of updates, send a test enquiry through your own form and make sure it lands in your inbox.
How Do You Stop WordPress Updates Breaking Your Site?
Take a backup before every update, and confirm that it actually restores.
Update one thing at a time, so that if something breaks you know exactly which update did it.
Test larger updates on a staging copy of the site first, if your host provides one.
Cut the plugin count. Every plugin removed is one less thing that can break, and one less thing that can be exploited, which matters given how many hacked WordPress sites trace back to an old plugin.
Check when each plugin was last updated by its developer. Anything untouched for a couple of years is a liability.
Why Do WordPress Updates Keep Breaking Irish Business Sites?
A typical small business site runs code written by dozens of unrelated developers. WordPress itself, the theme and every plugin are built separately, tested separately and updated on their own schedules. Nobody tests your particular combination except you, on your live site, usually when a customer tells you something is wrong.
More care reduces the odds, but it does not change how the platform works. Keeping a WordPress site healthy means someone checking it every month, indefinitely, and plenty of Irish owners were never told that when the site was built.
The lasting alternative is a site that has nothing to update. A static site built on Cloudflare has no plugins, no theme and no database, so there is nothing to break while you are not looking. I compare the two properly in Cloudflare vs WordPress, and why Irish businesses are moving away from WordPress covers the wider decision.
If your WordPress site broke after an update and you want to know whether it is worth patching or better replaced, a free website audit will give you an honest read, and you can always get in touch for a straight answer.
Want a straight answer about your own website?
Get a straight answer
