Guide · Maintenance · 5 min read
An update broke my website: the right reflexes, in order
In short: don’t run any other updates and don’t delete anything. Identify what was updated just before the failure, go back to the previous version of that item or restore the backup made before the update, then fix things calmly on a copy of the site. And for the future: updates one at a time, with a backup just before.
Why an update can break a website
A WordPress or PrestaShop website assembles parts from different sources: the software itself, a theme, plugins or modules, and PHP, the server’s language. Each one evolves at its own pace. An update may contain an error, or stop getting along with another part that has not changed.
Updates remain essential: many fix security holes. The problem is not updating, but doing it without a safety net.
Recognising the problem
| What you see | The likely cause | The first move |
|---|---|---|
| “There has been a critical error on this website”, on WordPress | A code error in a plugin or the theme | Follow the dedicated guide and the recovery email |
| A blank page or an “error 500” | A serious server-side error | Check the hosting error log |
| A broken layout | A theme or page layout tool that changed | Clear the caches, then check the theme |
| A broken feature: cart, form, payment | A plugin or module that became incompatible | Go back to the previous version of that item |
| “Briefly unavailable for scheduled maintenance” | An interrupted WordPress update | Delete the maintenance file left behind |
6 steps to recover
- Stop everything. Do not run other updates: each change makes finding the cause harder.
- Find what changed. Note what was updated just before the failure, and when. Your host may also have changed the PHP version: this has been common since version 8.1 stopped receiving security fixes at the end of 2025, and version 8.2 gets none after 31 December 2026; some older plugins do not support the later versions.
- Roll back that item. Reinstall the previous version of the plugin or module at fault, or deactivate it if the site can do without it for a few hours.
- Otherwise, restore the backup. The backup made just before the update puts everything back. Careful: orders or messages received since would be lost, so note them first.
- Fix on a copy. Once the site is back, replay the update on a copy of the site to find the real cause, without touching the site your visitors see.
- Tell the vendor. If the error comes from a plugin or module, report it to its vendor: a fix may follow.
The right order for updates
For next time, a simple routine prevents most failures:
Mistakes that make things worse
Updating everything at once
If ten items change at the same time, there is no way to know which one causes the problem.
Restoring without noting anything
Yesterday’s backup erases the orders and messages received since: note them before restoring.
Updating directly on the live site
Your visitors discover the failure before you do. A test copy avoids that.
Leaving automatic updates unmonitored
They are useful for security, but someone must check the site still works afterwards.
Postponing all updates
Out of fear of breaking the site, you let known security holes pile up: that is worse.
The routine before every update
- A full backup made the same day, and stored away from the server.
- The list of what is going to be updated, with the versions.
- A trial on a copy of the site, when the update is significant.
- One update at a time, at a quiet moment.
- A check right after: home page, form, cart, payment, emails.
- A note of what was done, to know what to undo if something goes wrong.
An update broke your website?
I put your website back on its feet, find the real cause, then offer you tested updates so it does not happen again. And you talk directly to the person who writes the code.
Let’s talk about your website See takeover and maintenance
Reply within one business day
Frequently asked questions
Should I turn off automatic updates?
Not the security ones, which matter. Better to keep them, with an automatic backup and someone who checks the site afterwards. Since version 6.6, released in July 2024, WordPress even rolls back, on its own, a plugin auto-update that crashes the site.
How do I go back to a plugin’s previous version?
For many plugins, older versions remain available on the official WordPress website. Otherwise, files can be restored from a backup.
My site shows “Briefly unavailable for scheduled maintenance”: what now?
An update was interrupted, and WordPress left a small file called .maintenance at the root of the site. In principle, WordPress lifts this block on its own after ten minutes; if not, delete the file from your hosting account. Then check that the update completed.
Is my data lost?
Rarely: an update mostly affects files. But make a backup before any repair attempt.
Who should do the updates?
You, if you follow the routine above, or a provider, under a clear contract: see what a good maintenance contract should include.
How much does a repair cost?
It depends on the failure and the state of the site. I never quote without looking first. Describe your project: I will send you a clear, itemised quote. Reply within one business day.
Sources
Keep reading
Slow website: the most common causes and how to fix them
WordPress or PrestaShop site too slow? How to measure its speed, the most common causes and the fixes, from hosting to images.
Preparing your website for holiday traffic peaks: the method for Black Friday and Christmas
From Black Friday to Christmas, your online store gets far more visitors. The timeline and the method to keep it fast, stable and ready to sell.
My WordPress site has been hacked: what to do, and in what order?
Redirects, unknown pages, a warning from Google? The right steps when your WordPress site has been hacked: secure it, clean it up, close the security hole.