You clicked Update. The site went white, or WordPress showed “There has been a critical error on this website.” Calls still come in. The form does not.
Do not reinstall WordPress from scratch. Do not buy a new theme in a panic. Do not keep hitting Update on everything else.
Most of these failures are a plugin or theme conflict after an update. WordPress has a built-in path for that. Use it.
If you do not have a recent backup habit yet, read WordPress backup before update after you are stable again.
First 15 minutes
- Try the site and `/wp-admin/` in a private window. Sometimes only the front end fails, or only one plugin’s page.
- Check email for the administrator address (Settings → General). Since WordPress 5.2, a fatal PHP error can trigger Recovery Mode: WordPress emails a special login link so you can reach the dashboard with the faulty plugin or theme paused. See WordPress.org documentation on Recovery Mode.
- If you get in: deactivate the plugin or theme named in the notice. Reload the site. Do not immediately re-enable it.
- If you get no email: you will work from hosting file manager or FTP. That is normal. You are not locked out of the files, only the dashboard.
If this is a customer-facing outage and you are not the technical owner, call the person who hosts the site or get a fix scoped before you rename random folders.
WordPress white screen after update
A WordPress white screen after update (blank page, no message) usually means a PHP fatal error with display turned off — or a broken theme/plugin still loading.
Calm order:
- Recovery Mode email, if it arrived
- Disable the last plugin you updated via files (below)
- Switch to a default theme only if the failure started after a theme update
- Restore yesterday’s backup if you cannot isolate the cause quickly
Take a screenshot of any error and note the time. If you hire help, that saves an hour.
WordPress critical error after update
When you see the WordPress critical error after update message, WordPress is telling you PHP crashed hard enough to stop the page.
That message is progress, not a dead end: it often pairs with Recovery Mode. Use the emailed link, disable the named plugin or theme, and confirm the front end loads before you troubleshoot further.
Do not update core, theme, and twenty plugins in one click while the site is already critical.
If you cannot log in: disable plugins from the files
On most hosts this is File Manager or SFTP. This is the standard way to fix WordPress after plugin update when the dashboard is unreachable.
- Go to `wp-content/plugins/`.
- If you know which plugin you updated, rename that folder (for example `some-plugin` → `some-plugin.off`). WordPress cannot load it.
- Reload the site.
- If you do not know which plugin, rename the whole `plugins` folder to `plugins.off`. The site should load with plugins disabled. Then rename it back and disable plugins one at a time from the dashboard — or keep folders renamed until you find the one that breaks the site.
Do the same for a theme only if the failure started after a theme update: rename the theme folder and WordPress will fall back to a default theme if one is installed.
Restore a backup if you have one
If the host has yesterday’s backup and you cannot isolate the plugin, restoring last night’s copy is better than editing the database by hand.
Then do not update everything on production again until you have a staging copy. The goal is a live site today and a safe update process tomorrow.
What caused it (so it happens less)
Typical chain:
- PHP version on the host is older than the plugin now requires — or newer than a neglected plugin supports
- Two plugins hook the same checkout or form
- A “suite” plugin updated and broke a page builder
- The theme was customized in a way that cannot survive a parent-theme update
This is why a lean plugin list and a maintenance rhythm matter. Updating 40 plugins on the live site on a Friday is how this article gets traffic.
Hosting matters too: WordPress hosting for small business. If the host has no staging and no backups, you are one update away from a weekend of file manager.
After you are up, run a security checker and a site audit on the homepage. A malware-infected site can also “break after an update,” but that is a different cleanup.
Prevent the next outage
- Keep a staging site. Update there first.
- Update plugins in small batches, not all at once.
- Drop plugins you do not use.
- Do not edit plugin files. They get overwritten.
- Know who receives the admin email. Recovery Mode is useless if that inbox is a dead employee.
- Back up before every live update batch.
Agencies that sell WordPress but do not want to be on call for fatal errors can hand the technical work to a partner — that is what agency partners is for.
When to stop DIY and call for help
Call a developer if:
- You cannot access files or host panel
- Restore points are missing or restore fails
- The site is hacked (spam links, mystery admin users) in addition to the update failure
- Ecommerce checkout is broken and revenue is on the line
- You have already renamed folders without a map of what you changed
WebSolNet handles emergency repairs through web development and ongoing WordPress websites care.
FAQ
Will renaming a plugin folder delete my data?
No. It stops PHP from loading the plugin. Settings usually stay in the database. You can rename the folder back after you have a plan.
Should I update WordPress core at the same time as plugins?
Not on a broken site. Get stable, then update on staging: core, then theme, then plugins, checking the site between groups.
The site is up but the form still fails.
That can be a plugin conflict without a full white screen. Disable the last form-related plugin you updated and test. Forms are web development / website fix work if you need it done without trial and error.
What if Recovery Mode email never arrives?
Check spam, confirm the admin email is current, then use file manager / SFTP to disable plugins. Do not wait indefinitely for an email that may never come.
Can a theme update cause a critical error?
Yes. Rename the theme folder only if the failure started after a theme update, and ensure a default theme is available as fallback.
How do I keep this from happening every month?
Staging + backups + small update batches + fewer plugins. If that still feels risky, put the site on a care plan so updates are not a Friday surprise.
Need help fixing your WordPress website?
WebSolNet does emergency WordPress repairs, plugin cleanup, and calmer ongoing maintenance so the next update is not a coin flip. See custom web development and website fixes, WordPress websites, or contact us. Call (850) 610-7214. Owner-operated remote US studio.
