Recovery: WordPress
One plugin update took the whole site down and nobody knows which one.
A white screen or a fatal error after an update almost always traces to one plugin conflicting with another, or with the theme. We isolate the exact cause safely on a copy of the site, not by disabling things on the live one and hoping.
- We isolate on a safe copy first
- Written cause before touching live
- No cost to see the scope
Evidence, then action
How we isolate the conflict
The evidence we pull first
We check the PHP error log for the exact fatal error and the file it points to, note which plugins updated right before the outage, and take a full backup of the current state before changing anything.
The triage order
First we put the site into maintenance mode or work on a staging copy so visitors are not looking at a broken page while we investigate. Next we deactivate plugins one at a time, starting with whatever updated most recently, checking after each one whether the error clears. Then we check the theme itself if no plugin alone explains it.
What usually fixes it
Rolling back the specific plugin that updated last, updating an outdated plugin that was actually incompatible with a newer WordPress core version, or resolving a direct conflict between two plugins doing the same job restores the site in most cases within a few hours.
What we cannot promise
We cannot promise a plugin's own developer will fix a bug on our timeline, since a genuine bug in a third party plugin needs a fix from whoever built it. We can promise to isolate exactly which plugin is responsible and a workaround while you wait on that fix.
The decision tree we run
If the error appeared right after an automatic update
we check the plugin change log against the outage time first, since the plugin that updated closest to when the site broke is the most likely suspect.
If the error message points at a specific file path
we trace that path back to the plugin or theme that owns it, since PHP fatal errors almost always name the exact file where the conflict happened.
If deactivating plugins one by one does not clear the error
we check the active theme next, since some conflicts sit between a plugin and the theme's own code rather than between two plugins.
If the site works on staging but breaks again on live
we check for a caching layer or a different PHP version between the two environments, since a fix that works in one place can fail in another for reasons unrelated to the plugin itself.
How the engagement runs
01
Backup and safe isolation
We back up the current state and move the investigation to a staging copy or maintenance mode so we are not troubleshooting on a page real visitors are seeing.
02
A written cause, plugin by plugin
You get a plain answer on which plugin or combination caused the conflict, based on testing, not a guess.
03
Fix, then confirm on live
We apply the fix on the live site and confirm every core page loads correctly before calling it resolved.
WordPress outage questions
A single plugin can register a function or a piece of code that another plugin or the theme also depends on, and if an update changes that piece even slightly, everything relying on it can fail at once. This is why a fatal error from one small update can take down an entire site rather than just one feature.
It is safer to do that on a staging copy or in maintenance mode rather than on the live site, since disabling the wrong plugin on a live site can create a second problem while you are still trying to solve the first. We always isolate on a safe copy before touching anything visitors can see.
The PHP error log usually settles this. If the error names a specific plugin file, that plugin or its conflict with something else is the cause. If the log shows a resource limit or a timeout with no plugin named, hosting capacity is more likely the real issue.
It can, especially if the same plugins keep updating independently of each other. Once we find the specific conflict, we can also set up a safer update process, such as testing updates on staging first, to catch this kind of issue before it reaches the live site.
Getting the site back up and finding the cause is scoped in a free proposal, and for a live outage we move quickly rather than waiting the full business day when it is urgent. Ongoing website maintenance after that is priced in the same proposal.
Get your site back up and find the real cause
Tell us what changed right before the outage and send us access. We will isolate the conflict on a safe copy first and report back with a fix.