A fatal error after an update means the new code called something that no longer exists, or is not compatible with your PHP version. WordPress stops execution rather than render a broken page. The error message names the file and line, which is usually enough to identify the culprit precisely — the work is capturing it safely and deciding whether to roll back, patch, or replace.
Before you buy, one quick check
This is diagnostic and fully reversible. Nothing is deleted.
Think about what updated last — WordPress usually emails you, or the update history is in your host dashboard. Over SFTP, go to wp-content/plugins and rename that one plugin folder by adding -off to the end. Load your site.
Site comes back — you have found it. Rename the folder back so nothing is left half-disabled, and tell us the plugin name when you order.
Still broken — it is something else, possibly the theme or core. Rename it back and buy this fix.
Rename only one folder, and put it back either way. Deactivating plugins for long periods can clear scheduled tasks and temporary data.
Fatal PHP error after update
An update introduced a fatal PHP error and took the site down. We capture the exact error, roll back or patch the failing component, and verify the site loads on every template.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Broke right after a plugin or theme update | This fix covers it |
| Blank page with no update in the last week | White screen of death |
| You just want the update undone, nothing else | Failed update rollback |
| Broke after the host changed PHP version | PHP version compatibility fix |
| Update failed halfway and left maintenance mode on | Stuck in maintenance mode |
What you are seeing
- A fatal error message, or a blank page, immediately after an update
- WordPress may have emailed you about a technical problem on the site
- The admin may still load, or may be down as well
- Deactivating the plugin from admin is not possible because you cannot reach it
Common causes
- The updated plugin requires a newer PHP version than your host runs
- Two plugins that both worked before are now incompatible with each other
- A plugin update dropped a function that your theme or a snippet still calls
- A premium plugin updated without a valid licence and shipped a partial file set
- The update was interrupted and left files half-written
What we do
- Take a full backup before touching anything
- Enable error logging and capture the exact file, line and function that failed
- Identify whether the fault is the update itself, a conflict, or your PHP version
- Roll back to the last working version, patch the incompatibility, or replace the component
- Check nothing else on the site depended on what changed
- Load-test every template and confirm the log stays clean
What is included
- A working site, verified on every template type
- A short incident note naming the exact cause, with the error text
- A recommendation on whether the update is safe to reapply, and when
- The pre-fix backup, kept for 30 days
- A free 9-layer scan with anything else we found
Not included
- Rewriting a plugin so it works with an unsupported PHP version
- Buying licences on your behalf, though we tell you what is needed
- Building replacement functionality if a plugin is abandoned — quoted separately
- Malware removal, design changes or content work
Questions about this fix
Will you just undo the update?
Only if that is the right answer. A rollback fixes today and leaves you on old code with the same problem waiting. Where the fix is a settings change, a PHP version bump or a compatibility patch, we do that instead and tell you why in the incident note.
What if the plugin is no longer maintained?
We say so plainly and suggest what to replace it with, including how much of your existing data would carry across. We will not leave an abandoned plugin running just because rolling back was quicker.
Can you stop this happening on the next update?
Not with this fix, which addresses the one that broke. What prevents it is testing every update on a staging clone before it reaches the live site, which is what a care plan does. If this is the second or third time, that is the real fix.
I do not know which update caused it. Is that a problem?
No. The error log names the failing file, which names the plugin or theme. You do not need to know in advance — it just saves us a few minutes if you do.
Could the update have damaged my content?
Very rarely, and we check. A fatal error stops execution before most write operations, so content is normally untouched. Where a plugin did run a database change before failing, the backup we take first means it can be reversed.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.