Troubleshooting · Troubleshooting
How to Fix a Theme Update That Broke the Site in WordPress
Short answer
A theme update breaks a site when the new version drops a feature, needs a newer WordPress or PHP version, or conflicts with a plugin. Switch to a default theme first to confirm the theme is the cause, then roll the theme back to the last working version or fix the conflict. Back up before you change anything, and test the update on a staging copy next time.
Key takeaways
- A broken site after a theme update usually means the new version needs newer WordPress, PHP, or plugin versions.
- Switching to a default theme proves the theme is the cause in under a minute.
- Recovery mode pauses a faulty theme for your browser only, so you can still reach the dashboard.
- WP-CLI can roll a theme back to a set version with wp theme update and the version flag.
- Child themes keep your custom code safe when the parent theme updates.
- WordPress checks for updates every 12 hours, so a new theme version may arrive a day late.
What does a broken site after a theme update look like?
A broken site after a theme update shows a blank page, a broken layout, missing menus, or a critical error message.
The front end may load with no styling, while the dashboard still works, or both may fail at once.
The timing is the clue. If the site worked before the update and broke right after it, the new theme version is the prime suspect.
Note what changed just before the break, since the update log in Dashboard, then Updates shows the exact time and version.
What causes a theme update to break a site?
Four causes explain most breaks: a new theme version needs newer WordPress or PHP, a plugin conflicts with it, custom code in the parent theme was overwritten, or the update itself failed partway.
| Cause | Sign | Fix |
|---|---|---|
| Needs newer WordPress | Dashboard shows an update notice for core | Update WordPress first |
| Needs newer PHP | Fatal error names a PHP feature | Raise the PHP version |
| Plugin conflict | Break starts only with one plugin active | Update or replace the plugin |
| Custom code lost | Custom layout or code vanished | Move code to a child theme |
| Failed update | Site stuck or files missing | Reinstall the theme by hand |
A child theme keeps custom code safe, since WordPress.org notes that customizations in a child theme survive when the main theme updates, as the FAQ Troubleshooting page explains.
Theme updates can also drop support for an old WordPress version, so check the theme page for its tested-up-to version before you update.
WordPress.org recommends PHP 8.3 or greater (checked November 2026), so a theme that needs a newer PHP version will fail on an old host.
WordPress checks for updates every 12 hours, so a theme update notice can arrive a day after release, as WordPress.org notes in the FAQ Troubleshooting page.
How do you confirm the theme is the cause?
Switch to a default theme and reload the site; if it loads, the updated theme is the cause.
- Open Appearance, then Themes in the dashboard, if you can reach it.
- Activate a default theme such as Twenty Twenty-Four.
- Reload the front end in a private window.
Twenty Twenty-Four is a known default theme, listed as valid in the Health Check plugin changelog, so it is a safe stand-in, as the Health Check plugin notes.
If the site still fails on the default theme, the cause is a plugin or the server, not the theme.
Test with plugins off as well, since a plugin can break only when the new theme loads it.
A blank front end with no message may be a server error instead, so check our guide to the 500 Internal Server Error.
How do you get the site back with a default theme?
If you cannot reach the dashboard, rename the broken theme folder by SFTP and WordPress falls back to a default theme.
WordPress.org explains that renaming the active theme folder in wp-content/themes makes WordPress switch to a default theme, as described in Common WordPress Errors.
- Connect by SFTP and open wp-content/themes.
- Rename the broken theme folder, for example mytheme to mytheme-old.
- Reload the site and confirm the default theme loads.
Your content stays in the database, so switching themes does not delete posts, pages, or media.
If the dashboard shows a critical error screen instead, use the recovery email WordPress sent to the admin address.
Make WordPress Core explains that recovery mode emails the admin a secret link and pauses the faulty theme for that browser only, as described in the recovery mode announcement.
How do you roll back to the last working theme version?
Rolling back means installing the last working version of the theme over the broken one.
WP-CLI can install a set version with wp theme update and the version flag, as the WP-CLI theme update docs show.
wp theme update mytheme --version=1.4.2
Replace mytheme with your theme folder name and 1.4.2 with the last version that worked.
Without WP-CLI, download the older version from the theme vendor or WordPress.org theme page, unzip it, and upload it by SFTP over the broken folder.
If the vendor removed the old version from its site, use the copy in your last backup instead.
Back up first, since a rollback replaces theme files. Our guide to restoring a backup with UpdraftPlus covers the restore steps.
How do you fix the conflict instead of rolling back?
Fixing the conflict keeps you on the new version, so try it when the theme is otherwise worth keeping.
WordPress 7.1.5, released 18 November 2026, is the latest version, with 7.2 planned for 10 December 2026, according to the WordPress versions page.
- Update WordPress core first, then update every plugin.
- Reactivate plugins one at a time and reload the site after each one.
- Check the theme changelog for dropped features or new requirements.
- Raise the PHP version if the theme needs it.
If the theme needs newer PHP, our guide to updating the PHP version in WordPress walks through the change.
A fatal error line in wp-content/debug.log names the file at fault, so enable WP_DEBUG and WP_DEBUG_LOG, reload once, and read the log, as Debugging in WordPress explains.
If memory runs out during the update, PHP defaults to a 128M limit, so raise it or ask the host, as the PHP manual shows.
If the memory error keeps appearing, see our guide to the allowed memory size exhausted error.
Contact the theme author with the debug log line if the conflict is in the theme itself, since only the author can fix theme code.
How do you update safely next time?
Test every theme update on a staging copy before you run it on the live site.
- Back up files and the database before the update.
- Read the theme changelog for breaking changes and new requirements.
- Update WordPress core and plugins first, then the theme.
- Check the site right after the update, before you move on.
Schedule updates for a quiet hour, so a break affects fewer visitors while you fix it.
If the update stalls and the site shows a maintenance message, see our guide to the briefly unavailable for scheduled maintenance error.
Block themes and classic themes update in different ways, so know which type you run; our block theme vs classic theme guide explains the difference.
How do you confirm the site is fixed?
The site is fixed when the front end loads with styling, menus, and widgets in place.
- Open the home page and two inner pages in a private window.
- Check menus, sidebars, and the footer for missing items.
- Submit a form and load the checkout page if you run a store.
- Turn off WP_DEBUG when you finish.
Keep the default theme installed as a fallback, since WordPress needs one to fall back to.
Ask a friend on another network to load the site too, since your own browser cache can hide a broken page.
What mistakes should you avoid?
Avoid five mistakes that turn a broken theme into a longer outage.
- Do not edit the parent theme directly; move custom code to a child theme first.
- Do not update the theme on the live site without a backup.
- Do not delete the broken theme folder before you copy your custom code out of it.
- Do not ignore the theme changelog, since it often names the breaking change.
- Do not leave the default theme active as a fix; restore or repair your real theme.
Write down each step you take, so you can undo the last change if the site gets worse.
Frequently asked questions
Can I just reinstall the same theme version?
Yes, if the update itself failed partway. Download a fresh copy of the same version from the vendor or WordPress.org, upload it by SFTP over the broken folder, and reload the site. If the files were fine, the break is a conflict instead.
Will switching themes delete my content?
No. Posts, pages, and media live in the database, so they stay put when you switch themes. Theme settings, widgets, and menus may need to be set again, so note them down before you switch.
How do I know which version my theme was on before?
Open the theme folder and read style.css, which lists the version at the top, or check the dashboard update notice email. If you kept a backup, the old version is in the backup files.
What if the theme vendor no longer supports my theme?
Pick a supported theme with the same layout, move your custom code to a child theme, and test the switch on staging. An unsupported theme stops getting security fixes, so staying on it is a risk.
Why did the update work on staging but break the live site?
Staging and live often differ in PHP version, memory limit, or active plugins. Compare the two in Site Health, then match the live server to staging before you update again.
When should I call my host?
Call your host when the site fails on a default theme, when you cannot raise the PHP version or memory limit, or when the error log points to a server setting. Send them the debug log lines for a faster answer.
Sources
- Common WordPress Errors WordPress.org
- FAQ Troubleshooting WordPress.org
- Debugging in WordPress WordPress Developer Resources
- Health Check & Troubleshooting WordPress.org
- Fatal Error Recovery Mode in 5.2 Make WordPress Core
- WordPress Versions WordPress.org
- wp theme update Developer.WordPress.org
- Description of core php.ini directives PHP Manual
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.
