PHP and Runtime Upgrades You Cannot Keep Postponing
Every site runs on a language runtime with a support lifecycle. When that version reaches end of life it stops receiving security fixes, and eventually your host will upgrade it for you, on their schedule, with a notice period you may not read.
Why it gets postponed
Because nothing appears to be wrong. An old runtime serves pages perfectly well right up until a plugin drops support, a host forces the change, or a vulnerability is disclosed with no patch coming. The cost of postponement is that the eventual upgrade happens under time pressure instead of on a calm afternoon.
What actually breaks
- Abandoned plugins using functions removed in newer versions.
- Custom code written years ago by someone no longer available.
- Themes that were never updated after purchase.
- Integrations relying on old library behavior.
Note the pattern: the risk is concentrated in software nobody maintains. If everything on your site is actively maintained, upgrades are usually uneventful.
The safe sequence
- Check what version you are on and when it reaches end of life. Your host's control panel shows the first; the language's own site shows the second.
- Update every plugin and the theme to current versions first, on staging.
- Switch staging to the new runtime version and click through everything: forms, checkout, admin screens, any custom feature.
- Read the error logs, not just the pages. Warnings that do not break the display today become fatal in the next version.
- Fix or replace whatever fails. This is where abandoned plugins get retired, which is a benefit, not an obstacle.
- Take a backup, switch production, and re-test the critical paths immediately.
Make it routine
Check your runtime version every six months and plan to move one major version at a time rather than jumping three at once. Sites that upgrade regularly do it in an hour; sites that have not upgraded in five years turn it into a project with a budget. It is the same work either way, just distributed differently.
