If a WordPress site breaks after an update, first record the exact error and what changed, then use Recovery Mode or a controlled plugin/theme isolation to regain access. Avoid making several changes at once. Restore a suitable backup if the update damaged files or the database, and test the site before trying updates again.
Start with the symptom and protect your options
Write down what was updated, when it happened, which pages or features fail, and the exact message shown. Check whether the public site, the dashboard, or both are affected. Keep any WordPress error email and relevant hosting logs; they may identify the component or failure.
- Make one change at a time so you can tell whether it helped.
- Before attempting a rollback or changing files, confirm that you can access a usable backup. WordPress recommends backing up before updates; its update guidance explains that a failed upgrade may require restoring a backup and, where appropriate, previous-version files.
Use Recovery Mode for a “critical error”
For a fatal PHP error during a regular page load, WordPress may email the site administrator a Recovery Mode link with information about the error. Recovery Mode, introduced in WordPress 5.2, lets the administrator enter the dashboard while the identified faulty plugin or theme is paused for that administrator’s session. See the WordPress.org Recovery Mode documentation.
- Open the Recovery Mode email and follow its special login link. If it is missing, check spam and confirm which address is configured as the site administrator. Email delivery is not guaranteed.
- Read the dashboard notice to identify the component WordPress reports, then temporarily deactivate it.
- Check whether the site loads again. Deactivation can restore access, but it does not fix the component’s underlying defect or compatibility problem.
- After making a repair, exit Recovery Mode and test the site in a normal session.
Recovery Mode does not cover every failure. WordPress documents it for fatal PHP errors during regular page loads, not errors in cron or other background tasks. If no email arrives, continue with the access and isolation steps below.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall#1 Best Overall
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
If you cannot reach the dashboard, isolate plugins and themes
When login is unavailable, WordPress documents using FTP or a hosting file manager to rename the directory of a suspected plugin temporarily. Its troubleshooting FAQ also describes ways to disable plugins without administration-screen access. If you are unfamiliar with file or database operations, ask your host or a WordPress professional to help; an incorrect change can disrupt the site further.
- Use Recovery Mode’s error details, an email, or a log to narrow down the likely plugin or theme.
- In FTP or the host’s file manager, rename only the suspected component’s folder so WordPress cannot load it. If the site recovers, that is useful evidence, not proof that renaming solved the defect.
- If the culprit is unknown, follow the WordPress troubleshooting FAQ’s procedure for disabling plugins without dashboard access, or ask the host for help.
- Once access returns, check the component’s own documentation and compatibility information. WordPress’s plugin management guidance points to compatibility and diagnostic resources. A plugin that has not been updated for the current core release may be incompatible, but a lack of an update alone does not establish the cause.
Choose between repairing the component and restoring a backup
When one plugin or theme appears responsible
Look for a compatible release, follow the developer’s repair instructions, or contact its support. If the component cannot be made compatible, consider a maintained alternative. Re-enable it only when you are ready to retest the site.
When core files or the database may be damaged
Use a known-good backup appropriate to the failure. A full site backup may include both files and the database; restoring only one can leave them out of sync. WordPress says core upgrades overwrite included core files and recommends backing up before updating. For a failed post-upgrade site, consult its version-specific update and recovery instructions rather than copying arbitrary files over the installation.
The exact restore process depends on your host and backup system. Confirm what the backup contains and which parts of the site changed before restoring; ask the provider for help with database or hosting-level recovery.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Fix a lingering “Briefly unavailable for scheduled maintenance” screen
If an update has stopped but the site remains on the “Briefly unavailable for scheduled maintenance” message, a leftover .maintenance file may be responsible. First make sure the update process has actually stopped. WordPress’s update documentation says to remove the file from the WordPress directory over FTP. Then load both the public site and dashboard to see whether the update completed or needs further repair.
Check PHP, connectivity, and update status
Open Tools > Site Health in the dashboard and review notices about background updates, PHP, plugin updates, or connection to api.wordpress.org. Site Health findings help narrow the investigation; they do not, by themselves, prove what caused the break. WordPress explains these checks in its Site Health screen documentation.
PHP runs at the server level, so its version is controlled by your hosting provider—not by a standard WordPress dashboard setting. WordPress advises backing up and checking WordPress, theme, and plugin compatibility before changing PHP. Contact your host about a server-level PHP change or restore. The WordPress PHP guidance includes dated version examples, so check current compatibility information instead of treating those examples as current recommendations.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the repair before resuming updates
Once you regain access or restore the site, test the parts that matter to your visitors and business:
Best Value
- Free WordPress Hosting Guide Android Application. It Contains: A Brief Overview of WordPress Hosting, 9 Major Benefits of Managed WordPress Hosting.
- 5 Simple Steps to Choose WordPress Hosting, How to Maximize Your WordPress Hosting and Blogging Success, How to Choose the Best WordPress Hosting Provider, Optimize Your Blog with VIP Word.
- Press Hosting, What You Should Know to Choose the Best WordPress Hosting and Much More.
- The front page and representative inner pages.
- Dashboard login and the administrative screens involved in the failure.
- Forms, checkout, or other critical workflows your site relies on.
- Browser console and network behavior relevant to the original symptom.
If a change seems not to appear, check relevant caches; cached pages can make an update or repair look absent. Re-enable plugins and themes in a controlled sequence, testing after each change. Before retrying updates, confirm that you can access backups and restore support. WordPress recommends regular backups before enabling automatic plugin or theme updates; see its auto-update guidance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
