PHP Version or Compatibility Problem
Your site breaks or warns about compatibility because the hosting PHP version changed, or your software is too old — or too new — for the version running.
Common signs of this issue
- The site broke — errors, white screen, or 'critical error' — right after the host changed PHP versions (often announced in an email nobody read).
- A dashboard warning says your PHP version is outdated, unsupported, or insecure.
- A plugin, theme, or update refuses to run, stating it needs a newer (or older) PHP version.
- Errors on screen or in logs mention "deprecated," "syntax error," or "fatal error" with a PHP version flavor.
- An old site that hadn't been touched in years suddenly broke 'by itself' — the classic sign the host retired its PHP version.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Find your current PHP version — cPanel's "Select PHP Version" / "MultiPHP Manager," or your platform's health screen (WordPress: Tools → Site Health → Info) — and just note it. Diagnosis first, switches later.
- Check your email (and spam) for the host's PHP upgrade announcement — hosts nearly always notify before retiring versions, with dates. That email is your timeline and often your rollback instructions.
- Collect the specifics: which plugin/theme names a required PHP version, and what the exact error text says. "Deprecated" warnings are advance notices (annoying, rarely fatal); "Fatal error" lines name the failing file — usually identifying the incompatible plugin directly.
- Establish your target: currently-supported PHP (8.x) is where security fixes live. If your site only runs on a long-dead version (7.x or older), the site's software — not the host — is the thing that needs modernizing.
- Confirm a backup exists before any version switch — and prefer testing the switch on a staging copy (many hosts offer one-click staging) rather than experimenting on the live site.
- If the site is currently down after a forced upgrade: check whether the host still offers the previous version as a temporary choice in the PHP selector — stepping back one version is a legitimate short-term move to get back online while compatibility gets fixed properly.
What this usually means
PHP is the language your site's software runs on, and versions retire on a schedule: old ones stop receiving security fixes, so hosts eventually force-upgrade everyone. When that breaks a site, the real story is almost always one or two outdated plugins or an old theme that never got updated for the new version — the rest of the site is usually fine.
The sustainable fix order: update all software to current versions (most active plugins/themes support current PHP), replace anything abandoned by its developer, THEN run the supported PHP version. Rolling back PHP is a tourniquet — legitimate for getting back online today, wrong as a permanent home, because retired PHP means unpatched security holes and the host will eventually remove the option anyway.
A site that can only run on ancient PHP is announcing deferred maintenance: abandoned plugins, an unsupported theme, years of skipped updates. The PHP break is the invoice arriving. Modernizing costs a focused session or two now; deferring again re-runs this crisis on a shorter fuse with fewer rollback options.
What not to do
- Don't flip PHP versions repeatedly on a live site hoping one works — each flip can break differently; test on staging, change deliberately.
- Don't settle permanently on a retired PHP version — it's unpatched and the host will eventually delete the option mid-crisis rather than on your schedule.
- Don't change versions without a backup and a way back — the selector is easy to use in both directions, but only if you know what you changed from.
- Don't mass-update every plugin AND switch PHP simultaneously — one change at a time, or a failure can't be attributed.
- Don't edit plugin code to silence deprecated warnings — updates overwrite hand-edits, and the proper fix is a current plugin version.
When to get help
The awkward middle — old site, several outdated components, host deadline looming — is exactly where an experienced hand is efficient: they'll inventory compatibility, update or swap the blockers, test the switch on staging, and land you on supported PHP in a session or two. If your site is down right now from a forced upgrade, the quick sequence (step back a version, fix compatibility, step forward) is routine work; ask for exactly that.
Could your hosting be the problem?
If your host is slow, unreliable, or hard to deal with, moving to a better one can clear up issues like this for good. One we genuinely recommend is Instant Access Internet Services — a smaller, compassionate company with 30 years in the business, known for being one of the fastest, with great management and low pricing. (Just a recommendation — no affiliate link, no kickback.)
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
My host changed PHP and the site broke — why?
Hosts retire PHP versions when they stop receiving security fixes. Your theme or a plugin wasn't compatible with the new version and crashed. The fix: temporarily step back a version if offered, update/replace the incompatible components, then move forward to the supported version.
Can I just pick the newest PHP version?
Only if your software supports it — newest isn't automatically compatible, especially with older themes and niche plugins. Current-but-not-bleeding-edge (whatever your platform recommends) is the usual sweet spot. Test on staging when possible.
What do 'deprecated' warnings mean — is my site broken?
Not yet. Deprecated means 'this code style is scheduled for removal in a future PHP version' — an advance notice, not a failure. It IS a to-do: the plugin producing them needs an update before the next PHP jump turns warnings into fatal errors.
Is staying on old PHP really a security risk?
Yes — retired versions receive no security fixes, so every vulnerability found afterward stays open on your server. Old PHP also blocks plugin updates, which is the other main way sites get compromised. Supported PHP is foundational security, not pedantry.
How do I find which plugin is incompatible?
The fatal error names a file path — the folder name in it is usually the plugin. On staging, switch PHP and deactivate plugins one at a time to confirm. Plugin pages on wordpress.org also list tested PHP versions, and abandoned plugins (no updates in a year-plus) are the usual suspects.
Does a newer PHP version make my site faster?
Genuinely, yes — modern PHP (8.x) runs meaningfully faster than old versions, which for a dynamic site translates to quicker server responses. It's one of the few upgrades that improves security and speed simultaneously — once compatibility is sorted.