On December 31, 2026, the PHP project ships the last security updates for PHP 8.2. After that there are no official patches for 8.2, not even for critical vulnerabilities. Plenty of WordPress sites still run on 8.2, simply because everything worked and nobody had a reason to touch it.
The good news: for most sites, moving to 8.3 or 8.4 is one click and five minutes of clicking through the site. For some, one old plugin gets in the way. This article shows how to find out up front which group you’re in, and what to do if something breaks anyway.
The dates at a glance
| Version | Security updates until | Status in November 2026 |
|---|---|---|
| PHP 8.1 | Dec 31, 2025 | end of life |
| PHP 8.2 | Dec 31, 2026 | security updates only, ends in a few weeks |
| PHP 8.3 | Dec 31, 2027 | security updates only |
| PHP 8.4 | Dec 31, 2028 | fully maintained until the end of 2026, then security updates |
| PHP 8.5 | Dec 31, 2029 | fully maintained |
Source: php.net — Supported Versions. PHP 8.6 is scheduled for November 19, 2026.
WordPress itself isn’t the obstacle: according to the WordPress compatibility table, the current release 7.1 is fully compatible with PHP 7.4 through 8.5. WordPress recommends at least PHP 8.3, and according to the hosting handbook 8.4 or 8.5 for new installations (with us, currently up to 8.4). What breaks is almost always plugins and themes, not WordPress.
What this means with us
At xaweho, PHP 8.2 stays selectable after December 31, 2026 and keeps getting security updates through Extended Lifecycle Support (ELS), at no extra charge. That applies to Plesk Web Hosting and LiteSpeed Web Hosting alike, and also to the end-of-life versions offered there: 7.4 through 8.1 on Plesk Web Hosting, 8.1 on LiteSpeed Web Hosting. Nothing gets switched automatically: on January 1 your site runs on the same PHP version as on December 31, just still patched.
You should still switch, just without the deadline pressure:
- Plugins move on. Plugin developers test against current PHP versions and raise their minimum version over time. At some point the update you need will only exist for 8.3 and newer.
- ELS means security, not development. Vulnerabilities get fixed; new features and performance improvements don’t arrive anymore.
- This repeats. PHP 8.3 ends in late 2027. Move to 8.4 calmly now and you’re set until the end of 2028.
If you’re with another host: ask them what happens to 8.2 on January 1. Some providers switch end-of-life versions automatically, others charge a monthly fee to keep them running. You want to know either one in advance, not from an invoice or a broken site.
1. Check what’s running in two minutes
In WordPress, go to Tools → Site Health, open the Info tab and expand the “Server” section. “PHP version” tells you what your site is running on right now.
Don’t rely on a warning box in the dashboard: WordPress only shows “PHP Update Required” for much older versions. PHP 8.2 isn’t one of them (as of November 2026). So no box doesn’t mean all clear.
In Plesk you see the version per domain under Websites & Domains → domain → Hosting & DNS → PHP Settings. The details are in Choosing and setting the PHP version.
2. Plugin traffic light: which extension will cause trouble?
Before you change anything, bring everything up to date: WordPress, all plugins, all themes. Most of the time the problem is a plugin that has had a fitting update for ages.
Then go through your plugin list once and look up each plugin’s page in the WordPress plugin directory:
- Green: updated within the last year, tested with the current WordPress version. Nothing to do.
- Yellow: no update for over a year. Often still works, but it’s the first suspect if something jams after the switch.
- Red: the directory warns that the plugin hasn’t been tested with recent WordPress releases, or it has been closed. Find a replacement now, not when it breaks.
Common pitfall: purchased themes and premium plugins with an expired license. They don’t show up in the plugin directory at all and get no updates without a valid license. If your site uses a commercial theme from 2021 that was never updated since, that’s where your biggest risk is.
3. Test first, then switch
Back up first. With us, an automatic backup runs every day with 7 days of retention, and you can restore it yourself in Plesk. A fresh manual backup before the switch is still worth it, see Creating backups and restoring.
Then you have two options:
Option A: test copy with the WordPress Toolkit. The Toolkit clones your site including the database to a subdomain, for example staging.yourdomain.com. There you set PHP to 8.4 and click through everything. The live site doesn’t notice a thing. With us, the Toolkit is included in Plesk Web Hosting from the Pro plan up and in every plan of LiteSpeed Web Hosting. The steps are in WordPress Toolkit in Plesk. Turn off search engine indexing for the copy, or the test site ends up on Google. And deactivate newsletter and mailing plugins on the copy: it takes over scheduled tasks and could otherwise send real emails to your customers.
Option B: switch directly, with a way back. Without the Toolkit, you switch the live site at a quiet time and check right away. Changing the PHP version in Plesk takes effect immediately and can be reverted just as fast. For small sites without a shop that’s perfectly fine. For a shop with orders coming in, take option A. On the Plesk Start plan without the Toolkit, Softaculous can clone the site as well if WordPress was installed through it, see Installing apps with Softaculous. Otherwise, open a ticket.
What to click through after switching:
- Home page and two or three subpages, including an older one
- Actually submit the contact form (does the email arrive?)
- Log in to the WordPress admin, open a post and save it
- For shops: add a product to the cart, go through checkout until just before payment
- Search, gallery, slider, newsletter sign-up: whatever your site has
If everything works, you’re done. If you went with option A, now switch the live site and run through the list there once more.
4. Emergency plan: “There has been a critical error on this website.”
Often it continues with “Please check your site admin email inbox for instructions.” Either way, it’s WordPress-speak for “a plugin doesn’t get along with the new PHP version.” No reason to panic, your data isn’t gone.
1. Switch back: set the domain’s PHP back to 8.2 in Plesk. The site works again immediately. Now you have time.
2. Check the inbox: when this happens, WordPress sends an email with the subject “[Your site name] Your Site is Experiencing a Technical Issue” to the admin address. It says which plugin or theme caused the error. That’s the information you need. The email also includes a link to recovery mode: it lets you log in despite the error and deactivate the plugin. You only need it if you can’t switch back or want to stay on the new version. Check the spam folder too. Common pitfall: the admin address is a mailbox nobody has read in years.
3. Read the error log if no email arrives: in Plesk, the domain’s Logs show the error with “PHP Fatal error” and a file path. The folder name after wp-content/plugins/ gives away the plugin, after wp-content/themes/ the theme.
4. Update or replace the culprit, then repeat the switch.
If you can’t get into the admin at all, you can deactivate a plugin without WordPress: in the Plesk file manager, rename the folder wp-content/plugins/pluginname to pluginname.off. WordPress no longer finds the plugin and turns it off. Later, update or replace it first, then rename it back and reactivate it under Plugins. Its settings are kept.
Which version should you pick?
PHP 8.4, if your plugins play along. For actively maintained sites that’s the normal case, and you’re set until the end of 2028.
PHP 8.3, if an important plugin still throws warnings on 8.4. A good intermediate step, but 8.3 already ends in late 2027.
You don’t need to jump in stages. Going from 8.2 straight to 8.4 isn’t riskier than two separate steps, it just means testing once instead of twice.
Frequently asked questions
Do I have to switch right now at xaweho? No. PHP 8.2 stays selectable with us and keeps getting security updates via ELS, at no extra charge. We still recommend switching over the next few months, because plugins keep raising their minimum versions.
Will you switch my site automatically? No. Your domain’s PHP version stays the way you set it. You decide when to switch.
Can I go back if something doesn’t work? Yes, any time and instantly. The PHP version is set per domain and takes effect when you save. No data is lost when switching.
What about Joomla, TYPO3 or custom software? Same procedure: update first, then test, then switch. Which PHP versions your release supports is in its system requirements.
I’m stuck with the error log. Open a ticket with the domain and the time of the error. We’ll look at the log and tell you which plugin or theme it is.
My host is dropping 8.2 or wants money for it. Now what? First of all: you can do the switch from this guide with any host. If you want to move anyway: in Plesk Web Hosting and LiteSpeed Web Hosting you pick the PHP version per domain yourself, end-of-life versions keep getting security updates via ELS at no extra charge, and we can move your WordPress site for you, see Migrating WordPress to xaweho.
What’s next
Next steps
Choosing and setting the PHP version
Which PHP version for which application. PHP selector in Plesk, php.ini settings (memory_limit, upload_max_filesize), switching without downtime.
WordPress Toolkit in Plesk
Plesk's dedicated WordPress Toolkit: staging, cloning, security scan, bulk updates, smart updates. Why it beats Softaculous for WordPress management.
Creating backups and restoring
The Plesk backup manager: daily automatic backups, manual backups, external backup targets, single-file restore, full restore.