How to Fix the WordPress “Critical Error” After a Database Update
WordPress “Critical Error” After a Database Update? Here’s What Actually Fixed It
Recently, a client reached out after updating WordPress and being immediately locked out of their site.
The update itself appeared to complete successfully, but as soon as they clicked “Update WordPress Database”, the site returned the dreaded message:
No admin access. No clear explanation. Just a broken site.
If you’ve run into this scenario, here’s what was really happening and how it was resolved.
The Symptoms
- WordPress core update completed
- Database update prompt appeared (normal after core updates)
- Clicking “Update WordPress Database” caused a critical error
- Front-end and
/wp-adminbecame inaccessible
This is one of those issues where WordPress gives very little surface-level information, but the cause is usually hiding just below the surface.
Step 1: Check the Debug Log (Don’t Guess)
Instead of troubleshooting randomly, I enabled WordPress debugging and checked the server’s error log.
That revealed the real issue:
PHP fatal error: allowed memory size exhausted
In plain terms: WordPress itself updated fine, but during the database update process, the site ran out of PHP memory.
The fatal error was being triggered by an object caching plugin during the update process, which pushed memory usage beyond the server’s configured limit.
Why This Happens After Updates
Modern WordPress sites are heavier than they used to be:
- Core updates temporarily load more data into memory
- Object caching plugins can amplify memory usage
- Hosts often default PHP memory to 128MB, which is no longer enough for many sites
So while everything worked before, the update process itself was the tipping point.
The Fix: Increase PHP Memory
The solution was straightforward once the cause was identified.
On the hosting server, I increased the PHP memory limit from:
- 128MB → 256MB
After that:
- The database update completed successfully
- The critical error disappeared
- WordPress admin access was restored immediately
No rollback required. No data loss. No plugin removal.
Why This Matters
This type of issue is easy to misdiagnose:
- It looks like a broken update
- It feels like a plugin conflict
- It’s tempting to panic and start disabling things blindly
But in reality, this was a server configuration issue, not a WordPress failure.
Knowing where to look, and what not to touch, is what keeps a small problem from becoming a big one.
If You’re Seeing This Error
If your WordPress site shows a critical error immediately after a database update:
- Check the debug or server error logs
- Look specifically for memory exhaustion errors
- Verify your PHP memory limit with your host
- Increase memory before undoing updates or deleting plugins
In many cases, that’s all it takes.
Final Thought
WordPress problems often look the same on the surface, but the causes can be very different.
This is why I always start with diagnostics instead of assumptions. It saves time, protects data, and gets sites back online quickly.
If you’re maintaining a WordPress site and want updates handled carefully (and recoverable when something goes sideways), this is exactly the kind of situation where experience matters.
Comments (0)