When a PHP Update Becomes Someone Else’s Problem
You built the website. You know the design. But when a routine PHP update brings WordPress down, who do you call?
Imagine you’re a freelance designer in Lisbon.
You’ve spent years building websites for your clients. You know how to make a business look good online, how to keep a client happy, and how to deal with the occasional WordPress update.
You’re not a server administrator. You never claimed to be one. And, until today, that was never a problem.
Then comes a security warning. The PHP version running on an old website needs to be updated.
It sounds straightforward. Log in to cPanel, select a newer PHP version, click Apply.
And suddenly, your beautiful WordPress website is gone.
Well, not exactly gone. The server is still there. The files are still there. The database probably hasn’t gone anywhere either.
But the website has turned into a blank page. The WordPress dashboard refuses to cooperate. Your client wants to know what happened.
Congratulations. You’ve just met Snow White and the Sleeping WordPress.
The website was old. The problem was complicated.
This is where people often underestimate WordPress.
A website that has been running for several years is rarely just WordPress. It may have an old commercial theme, plugins that depend on particular PHP features, database drivers, custom code, and components that haven’t been tested together for a long time.
Add an online shop, payment extensions and a handful of plugins, and you have several moving parts that may react differently to a change in the server environment.
The new PHP version might be perfectly fine. The problem could be an outdated plugin, an incompatible theme, a missing PHP extension, or several issues interacting with one another.
And if updating WordPress itself also fails because of an SSL certificate verification error, the simple task has just become a much bigger investigation.
This is not the moment to start clicking random settings and hoping for the best.
First, don’t panic. Then, don’t make it worse.
Recently, while working through a PHP upgrade on an older WordPress installation, I was reminded how quickly a routine maintenance task can turn into detective work.
The first PHP version I tried broke the site. Another allowed parts of it to work, but not the administration area.
The hosting control panel offered different PHP environments, and they didn’t behave identically. The available extensions and database drivers mattered. Updating WordPress presented another obstacle. And plugin compatibility had to be checked rather than assumed.
The way forward wasn’t one magical command.
It was a sequence of controlled changes, checking the result after each one, identifying what had failed, and restoring functionality without losing sight of the original security problem.
Eventually, the site was running on a supported, patched PHP release, with WordPress and its components updated. But getting there required more than changing a dropdown in cPanel.
A website loading again is progress. It isn’t proof that every function works, and it certainly isn’t proof that the website is secure.
Forms need testing. Logins need testing. If a shop is involved, its checkout and payment flow need testing too. Backups and the wider hosting configuration still matter.
The job isn’t finished just because the homepage has returned from the dead.
Dear designer, you don’t have to do everything yourself.
There’s nothing wrong with knowing your limits.
A good designer can build an excellent website without wanting to become an expert in PHP compatibility, server configuration, database drivers and WordPress recovery.
The same goes for marketing agencies, small web studios and independent professionals looking after websites for their clients.
You can be very good at your work and still need a specialist when something goes beyond your normal responsibilities.
In fact, knowing when to bring in another professional is part of doing the job properly.
The difficult part is finding someone who will take the problem seriously, explain what they’re doing, and understand that this isn’t just a website sitting on a server.
It’s your client’s business. And it’s your reputation, too.
Where Riskseeker comes in
At Riskseeker, I’ve spent years working at the intersection of websites, hosting, IT and security.
I understand that a designer calling for help doesn’t necessarily need another person to explain why updates are important. They probably already know.
They need someone to investigate the actual problem.
Someone who can look beyond the blank page, work through the hosting environment, identify compatibility issues, and help get the website back into a working and maintainable state.
No theatrical hacking. No pretending that every problem has a one-click solution. And no changing ten things at once and then guessing which one fixed it.
Just methodical troubleshooting, clear communication and respect for the fact that somebody else’s business depends on the result.
And yes, access to a hosting control panel is a serious responsibility. It should be handled securely, with only the permissions needed, through an appropriate access method. Trust isn’t an excuse to be careless with passwords; it’s a reason to be careful with access in the first place.
The real lesson
Security updates are necessary. Leaving vulnerable software untouched isn’t a sensible long-term strategy.
But updating an older website can expose years of accumulated technical debt — sometimes at the worst possible moment.
If you’re a designer or agency looking after client websites, you don’t need to solve every server problem alone.
You need to know who to call when the job stops being a design job.
And if your WordPress has gone to sleep after a PHP update, don’t assume that rebuilding the whole website is the only answer. First, find out what actually broke.
Snow White might need waking up. She doesn’t necessarily need a new castle.
If you need help troubleshooting your website you can contact me.
