Troubleshooting · Troubleshooting
How to Fix a Site Broken After a WordPress Update
Short answer
A site usually breaks after a WordPress core update because a plugin or theme conflicts with the new core version. Open the Recovery Mode email, deactivate the faulty plugin or theme, and check the error log to confirm the cause. If core files are damaged or the database upgrade failed, re-run the update or restore a backup from before the update.
Key takeaways
- A core update replaces WordPress core files and can run a database upgrade, so a plugin or theme that uses removed code can break the site.
- Recovery Mode, added in WordPress 5.2, pauses the faulty plugin or theme so you can log in and deactivate it.
- A full restore needs both files and the database, and the backup must come from before the update.
- WordPress 7.1.4 was released on 28 October 2026 as a security release that fixed 22 vulnerabilities, as of November 2026.
- Deleting the .maintenance file clears a stuck maintenance message, but it does not repair half-updated core files.
- Turn WP_DEBUG off again after you read wp-content/debug.log, so error details do not stay exposed.
What does “broken after a WordPress update” mean?
A site broken after a WordPress update stops loading, shows an error, or loses key features right after core files or the database were changed.
A WordPress core update replaces core files and can run a database upgrade. Your posts, pages, and media stay in the database, so a blank page usually points to code that no longer fits the new core version. The Updating WordPress guide from WordPress.org says you should always update to the latest version.
Common signs include a white screen, the message “There has been a critical error on this website”, or a front page that loads without its layout. Note the exact message and the time of the update before you change anything.
Why did the WordPress core update break your site?
A core update most often breaks a site when a plugin or theme uses code the new version removed or changed.
WordPress.org advises you to check that plugins and themes are compatible with the version you install, under Dashboard > Updates or Plugins > Installed Plugins. A plugin that has not been updated for the new core version can call a removed function or fail during the database upgrade.
An update can also stop halfway if the server times out, leaving mixed old and new files. A database upgrade can stop halfway too, so tables do not match what the new core expects.
| Symptom | Likely cause | First step |
|---|---|---|
| Critical error message | Plugin or theme fatal error after core change | Open the Recovery Mode email |
| White screen, no message | Fatal error with display off, or theme conflict | Turn on debug logging and read the log |
| “Briefly unavailable” message stays | Update stopped and left a .maintenance file | Check the site root for .maintenance |
| Admin loads, front page is broken | Theme or page builder conflict | Switch to a default theme for a test |
| Database upgrade prompt repeats | Database upgrade did not finish | Run the upgrade again from wp-admin |
What should you check first before you change anything?
Check the version, the error message, and whether you have a backup from before the update.
Open Dashboard > Updates if you can reach wp-admin, and note the WordPress version shown there. As of November 2026, WordPress 7.1.4 was released on 28 October 2026 as a security release that fixed 22 vulnerabilities, and WordPress 7.2 was planned for 8 December 2026.
Then check your email inbox and spam folder for a message from WordPress about a technical problem, because that email often names the faulty plugin or theme. Also check whether your host took a backup before the update, and note its date and time.
How do you use Recovery Mode after a core update?
Recovery Mode lets you log in to wp-admin with the faulty plugin or theme paused, so you can fix it without file access.
WordPress added Recovery Mode in version 5.2. When a plugin or theme causes a fatal error, WordPress sends the admin an email with a special link. Clicking it sets a cookie in your browser and pauses the faulty extension for you only.
Follow these steps in order:
- Open the admin email and click the Recovery Mode link, then log in.
- Go to Plugins > Installed Plugins and deactivate the plugin named in the email.
- If a theme is named, go to Appearance > Themes and switch to a default theme such as Twenty Twenty-Five.
- Click Exit Recovery Mode in the admin bar, then load your home page in a private browser window.
- If the site loads, update the faulty plugin or theme to a version that supports your WordPress version, or leave it off until its author releases a fix.
If no email arrived, check that the admin email in Settings > General is correct. Recovery Mode does not repair files or restore a backup, so use it to find the cause first.
How do you find the plugin or theme that conflicts with the new core version?
Find the conflict by reading the error log, then deactivate plugins one at a time until the site loads.
The Debugging in WordPress guide from Developer.WordPress.org explains the debug constants in wp-config.php. Add these lines above “That is all, stop editing!” after you back up wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Reload the broken page once, then open wp-content/debug.log in your file manager or by FTP. Look for lines that start with “PHP Fatal error” and note the file path, because the path names the plugin or theme folder. Turn WP_DEBUG back to false when you finish.
If you cannot reach wp-admin at all, rename folders by FTP or in your host file manager instead:
- Rename wp-content/plugins to plugins-old to switch off every plugin at once.
- Reload the site. If it loads, rename the folder back to plugins.
- Rename each plugin folder inside it one at a time, reloading the site after each change, until the break returns.
- Leave the faulty plugin folder renamed, then restore the rest and check the site again.
A default theme test works the same way. Rename your active theme folder in wp-content/themes, and WordPress falls back to a default theme if one is installed.
How do you clear a stuck maintenance message after an update?
Delete the .maintenance file in your site root only after you confirm the update is no longer running.
WordPress puts your site into maintenance mode during an update, and visitors may see the message "Briefly unavailable for scheduled maintenance. Please check back in a minute." The file is removed when the update finishes, so a message that stays for more than a few minutes usually means the update stopped.
Our guide on fixing the maintenance message covers this exact screen in more detail.
Follow these steps:
- Wait 10 minutes and do not click Update again while the first run may still be active.
- Open your host file manager or FTP client and go to the site root, the folder that holds wp-config.php.
- Look for a file named .maintenance and delete only that file.
- Reload the site. If the message is gone, open Dashboard > Updates and check whether the core version changed.
Deleting .maintenance does not repair half-updated files. If the site still shows an error after you remove it, treat the update as failed. Do not delete wp-config.php, wp-content, or the database while you do this.
How do you fix a failed core update and run the database upgrade again?
Re-run the update from a clean point, finish the database upgrade, and replace damaged core files only with the official package.
The Upgrading WordPress handbook from Developer.WordPress.org lists a safe order: back up the database, back up all WordPress files, deactivate all plugins, then download the WordPress package and replace core files. It also says you must not delete wp-config.php, wp-content, or your .htaccess file when you replace core files.
Use these steps:
- Make a copy of the current files and database now, even though the site is broken, so you can return to this point.
- Go to Dashboard > Updates and click Update Now if the button is still offered, then wait for it to finish without leaving the page.
- If wp-admin asks you to run a database upgrade, click the button and wait for the confirmation screen.
- If the dashboard update will not run, use the manual route in the handbook: download the latest WordPress package from WordPress.org, delete only the old wp-admin and wp-includes folders and the root core files, then upload the fresh copies.
- Go to Settings > Permalinks and click Save Changes to refresh rewrite rules after the files are replaced.
WordPress has applied minor and security updates in the background since version 3.7 on most sites. Major releases still need you to click Update Now, and four types of automatic background updates exist: core, plugin, theme, and translation file updates.
How do you restore a backup after a WordPress update?
Restore a backup only when diagnosis shows the site cannot be fixed by deactivating one plugin or theme, or when core files are damaged.
WordPress.org says you need both parts to fully restore a typical site: the files and the database. Backing up the files does not back up the database, because it lives outside the WordPress folder.
The same guide suggests weekly backups for smaller sites, daily backups for busy sites, and a backup always before an upgrade, with at least 3 to 5 recent backups in different places.
A restore throws away changes made after the backup point, so pick a backup from before the update. Posts, comments, orders, and settings added after that point will need to be added again.
Host restores differ by panel, but the pattern is the same:
- Kinsta takes automatic daily backups and stores them for 14 days on its entry plans, and its restore guide calls each backup a complete snapshot of files, database, redirects, and server settings. In MyKinsta, open the Backups tab and click Restore to next to the pre-update backup.
- WP Engine keeps 30 days of backups, and its backup and restore guide says a restore is destructive and overwrites files to match the backup point. In its User Portal, open Backups and choose Restore.
- SiteGround creates daily backups and keeps up to 30 daily copies on shared hosting, and its AutoUpdate guide says its tool makes a backup before every automatic update. In Site Tools, open Security > Backups to restore it.
If you use a plugin, the restore path is inside wp-admin when it loads. In UpdraftPlus, open Settings > UpdraftPlus Backups, scroll to Existing backups, and click Restore next to the pre-update set.
Our guide to restoring a backup with UpdraftPlus walks through those screens. If wp-admin will not load, use your host restore instead.
How do you know the fix worked?
Check the home page, wp-admin, and the main site functions in a private browser window after each change.
Load the home page, one post, and one page, then log in to wp-admin and open Tools > Site Health. That screen flags problems with updates, the database, and server settings, so fix any red items before you call the job done.
Then test the functions your visitors use:
- Submit the contact form and check that the message arrives.
- Add a product to the cart and reach the checkout page if you run a store.
- Check that images load and that menus link to live pages.
Clear any cache after the fix, including your caching plugin and any host cache, then reload the pages. If an error returns only on one page, check it again with the plugin off. For a 500 error that stays after the core fix, see our guide on fixing the 500 internal server error.
When should you contact your host?
Contact your host when the fault is on the server, when you have no file access, or when the database upgrade keeps failing.
Ask your host for help if the site shows a database connection error after the update, or if you cannot reach the file manager or FTP at all.
The Common WordPress Errors handbook from Developer.WordPress.org lists the white screen, internal server error, database connection error, failed auto-upgrade, and maintenance mode after an upgrade among the errors it covers.
Send the host the exact error message, the WordPress version before and after the update, the time of the update, and the lines from wp-content/debug.log that name the faulty file:
- Did the core update finish, or did it stop on the server?
- Can you restore the pre-update backup from your side?
- Is there a server error log entry for the time of the update?
- Did the database upgrade run, and did any table fail?
What mistakes should you avoid?
Do not run a second update, delete files at random, or restore the newest backup when the pre-update copy is the one you need.
- Do not click Update again while the first update may still be running, because two updates at once can leave mixed files.
- Do not delete wp-config.php, wp-content, or the database when you replace core files.
- Do not restore the backup taken after the update, because it holds the broken state.
- Do not leave WP_DEBUG on after you finish, because the log can expose file paths and error details.
- Do not update every plugin at once after the core fix, because you will not know which one broke the site if it fails again.
- Do not skip the backup before the next update. WordPress.org puts a backup before an upgrade in its update guide, and the backup guide shows how to make a full files-and-database copy first.
Frequently asked questions
Can I just update WordPress again to fix a broken site?
Only if the first update clearly stopped before it finished and no plugin or theme is named in the error. Re-running an update on top of a plugin conflict will not fix the conflict, and it can leave mixed files. Find the faulty plugin or theme first with Recovery Mode or the error log, deactivate it, then update again if Dashboard > Updates still offers the core update.
Will restoring a backup delete new posts or orders?
Yes, if they were added after the backup was taken. A restore returns files and the database to the backup point, so posts, comments, orders, and settings added after that point are lost unless you save them first. Pick the newest backup from before the update, export any new content you can still reach, and add it back after the restore.
What if I never got a Recovery Mode email?
Check the spam folder and confirm the admin email in Settings > General if you can reach wp-admin. Some hosts block the message, or the error happened before WordPress could send it. If no email arrives, use the debug log or rename plugin folders by FTP or in your host file manager to find the faulty plugin.
Should I switch off automatic updates after a break?
Not always. Minor and security updates have run in the background since WordPress 3.7 on most sites, and they close security gaps. Major releases still need a manual click, so you can leave minor auto-updates on and test each major release on a staging copy first. Turn off major auto-updates in Dashboard > Updates only if you want that control.
How long should I wait before deleting the .maintenance file?
Wait about 10 minutes and do not click Update again during that time. The file is normal while an update runs, and deleting it early will not stop a running update. If the message is still there after 10 minutes, the update has likely stopped, so you can delete the file from the site root and then check whether the core version changed.
Does a broken update mean my content is lost?
No, in most cases your content is still in the database. A core update replaces core files, not your posts, pages, or media records. Content is lost only if the database itself was damaged or you restore an old backup without saving newer posts first. Check the database with your host before you delete anything.
Sources
- Updating WordPress WordPress.org
- Upgrading WordPress Developer.WordPress.org
- Debugging in WordPress Developer.WordPress.org
- Common WordPress Errors Developer.WordPress.org
- How to Restore WordPress from a Backup Kinsta
- Backup and Restore WP Engine
- SiteGround AutoUpdate Tool Tutorial SiteGround
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
