PHP 8.2 End of Life: Check Your Website's PHP Version

Every release of PHP comes with a published support timeline, and PHP 8.2 reaches the end of its support window on December 31, 2026. If your website runs on it, nothing breaks automatically that day — PHP end of life doesn't shut a site down by itself, though a hosting provider may later change the PHP versions or policies it supports. What changes on the PHP project's side is that security patches stop for that branch, so any flaw reported afterward stays unpatched on 8.2. For a Philippine business running WordPress on shared hosting, this is a scheduled maintenance item rather than an emergency. Checking your current version takes about a minute; changing it in your hosting control panel is often just a few minutes' work, though backups, plugin checks, and testing can take longer. This guide covers what the December 2026 date means, how to check your version, how to move up carefully, and how to keep this from becoming a recurring scramble.

What Changes on December 31

PHP follows a fixed, openly published support schedule, which makes this easy to plan around. According to the official PHP supported versions page, each release branch gets two years of active support, where bugs and security issues are both fixed in regular point releases. After that comes two more years of security-only support, where patches are issued on an as-needed basis for critical security issues alone. Once those four years are up, the branch reaches end of life and receives nothing further.

PHP 8.2 was released in December 2022, and its active support ended on December 31, 2024 — so it has already spent the past year and a half in the security-only phase. December 31, 2026 is when that final phase closes.

Last verified: September 11, 2026. PHP support dates and hosting availability can change, so confirm the current PHP Supported Versions schedule and the versions offered by your hosting provider before making changes.

Which PHP version you can actually select depends on your hosting plan, not only on what the PHP project currently supports. PHP 8.5 is a currently supported upstream release, but availability depends on the hosting provider and plan. PHP 8.3 remains supported for security fixes through December 31, 2027, meets WordPress.org's current recommended baseline, and is currently the newest PHP version listed for Z.com PH Web Hosting.

How PHP Versions Fall Behind

Sites rarely end up on an older PHP version through neglect. More often, the version was simply set once during setup and never revisited, because there was no reason to. The site worked, so nobody touched it.

Sites Someone Else Set Up

A Facebook-first seller who hired a freelancer to build their store two years ago may never have logged into cPanel at all — the developer configured everything, handed over the login, and moved on. The same pattern shows up with sites built during a Ber-months push, where launching before the sale season mattered more than documenting server settings.

Plugins and Themes That Lag

Sometimes a version was deliberately held back because a booking plugin or an older payment integration threw errors on a newer PHP release. That was a reasonable call at the time, but it's worth rechecking now, since most actively maintained plugins have since caught up.

How to Check Your PHP Version

If your site runs WordPress, the fastest route is your own dashboard. Go to Tools → Site Health → Info, then open the Server section, and your PHP version is listed there. The Site Health screen will also show a recommendation if it considers your version outdated, so it doubles as a quick second opinion.

For any site, WordPress or not, your hosting control panel is the authoritative source. In cPanel, look for MultiPHP Manager or Select PHP Version under the Software section — it lists the version assigned to each of your domains. That per-domain detail matters if you run several sites on one account, since an old campaign landing page can sit on a different version from your main site.

If you can't find either, your hosting support team can confirm it for you in a single message.

Moving Up Safely

Once you know your current version, changing the PHP setting itself is quick — often just a few minutes in your hosting control panel. What takes longer, and matters more, is what happens around it: a backup you can actually restore, a check of plugin compatibility, and testing afterward. Start with that backup, taken the same day. Then check that the plugins doing real work — payment integration, contact form, booking tool, page builder — have been updated within the past several months. Don't assume a plugin is compatible just because it's actively maintained; check its published PHP compatibility (most listings on WordPress.org state supported PHP versions), especially for anything handling payments, bookings, or forms. A plugin untouched for two years is the piece worth checking or replacing first.

If your plan includes a staging environment, use it. Higher-tier plans such as Z.com Business Hosting include staging and cloning, so you can duplicate the site, switch the copy, and click through it before touching the live version. Without staging, reselecting the previous PHP version may provide a quick rollback when your hosting control panel allows it, but it does not replace a verified backup and restore plan. After changing the version in MultiPHP Manager, immediately test your homepage, a product page, your contact form, and your checkout or GCash payment page. If something looks wrong, reselecting the previous version often resolves a compatibility issue on its own — but if a change has already affected your database or files, you'll still need a verified backup and restore path to fully recover, which is why having one ready before you switch matters.

Quick Migration Checklist

Before switching:

• Confirm the PHP version assigned to each relevant domain.
• Create a same-day backup.
• Confirm where the backup is stored and how it can be restored.
• Update WordPress core, plugins, and themes where appropriate.
• Check compatibility documentation for payment, booking, form, page-builder, and other business-critical components.
• Identify abandoned plugins or old custom code.
• Use staging when available.
• Record the current PHP version.

After switching:

• Clear applicable website and server caches.
• Test the homepage and important landing pages.
• Submit contact and lead-generation forms.
• Test login and WordPress admin access.
• Test cart, checkout, and payment integrations, including GCash when used.
• Review Site Health and available error logs.
• Monitor the website after the change.
• If a critical function fails, use your planned rollback method and investigate before retrying.

Treat this as a practical starting point rather than a universal guarantee — adjust it to match your own site, plugins, and hosting setup.

Keeping PHP Current

This task is much smaller when it's expected. PHP publishes its dates years ahead, so one calendar reminder a year — ideally in a quiet month rather than during the Ber-months rush — keeps you ahead of every future end-of-life date.

Two habits help alongside that. Keeping plugins and themes updated reduces the likelihood of compatibility problems when you move to a newer PHP version, and choosing hosting that adds newer PHP versions as they're released keeps the decision in your hands. A WordPress Hosting environment built around managed updates handles more of this for you, which suits owners who'd rather not think about server settings at all.

Frequently Asked Questions