Start for free – your first 3 months are freeSee the offer

Databases and PHP

Why you should keep PHP up to date, and how to fix errors after a switch

See when PHP 8.2, 8.3 and 8.4 stop receiving security fixes, and how to find and fix errors if your website misbehaves after a switch.

3 min readUpdated

On this page
  1. How long are the versions supported?
  2. Get ready for a switch
  3. If the site fails after the switch
  4. Frequently asked questions
  5. Can I turn on the display of PHP errors on the page?
  6. Does Sitewig offer extended support for old PHP versions?
  7. What happens when PHP 8.2 has expired?
  8. Can I see the status of my version in the control panel?

Each PHP version receives security fixes for a fixed period. When the period ends, new vulnerabilities are no longer closed, and plugins start to require a newer version. So you should switch in good time, and know what to do if something misbehaves afterwards.

How long are the versions supported?

Timeline: 8.2 until 31.12.2026, 8.3 until 31.12.2027 and 8.4 until 31.12.2028
Support periods for the PHP versions Sitewig offers
VersionSecurity fixes up to and includingStatus in October 2026
PHP 8.231 December 2026Expiring soon
PHP 8.331 December 2027Stable
PHP 8.431 December 2028Stable

A version is called Expiring soon in the last year of its support period and Expired afterwards. If you run 8.2, plan a switch to 8.3 or 8.4 before the new year. Here's how: Change the PHP version on your web hosting.

Get ready for a switch

  1. Step 1: Make a copy

    Export the database, or check that there is a recent backup under Web hosting → Backup.

  2. Step 2: Update everything in WordPress

    Update WordPress, all plugins and your theme. Delete plugins you don't use – they can still cause errors.

  3. Step 3: Change the version

    Go to Web hosting → PHP, choose the new version and click Save.

  4. Step 4: Test thoroughly

    Click around the site, try the contact form and sign in to the admin area. If you have an online shop, place a test order.

If the site fails after the switch

If you get a white page, There has been a critical error on this website or a 500 error, it is almost always a plugin or theme that doesn't suit the new version.

Flow: read error.log, find plugin or theme, update or deactivate, or switch back
Troubleshooting in five steps
  1. Read the error log. For security reasons, PHP errors aren't shown on the page. They are written to the file logs/php/error.log in your web hosting's home folder. Open it with the File manager or SFTP and look at the last lines.
  2. Find the culprit. The error message contains a path: if it says e.g. wp-content/plugins/name/, the plugin is name.
  3. Update or deactivate. Update the plugin or theme. If you can't sign in to WordPress, rename the plugin's folder, e.g. to name-off, using the File manager, and WordPress will switch it off.
  4. Switch back temporarily. If it still doesn't work, choose the previous version under Web hosting → PHP and click Save. The site is then back up while you find a solution.
  5. Contact support. Send the last 10–20 lines from error.log, and we'll help you further.

Frequently asked questions

Can I turn on the display of PHP errors on the page?

Not from the control panel. Errors are never shown to visitors, as they can reveal details about your website. Use the error log instead.

Does Sitewig offer extended support for old PHP versions?

No. We only offer versions that still receive security fixes, and we are happy to help you move up to a newer one.

What happens when PHP 8.2 has expired?

It will no longer receive security fixes, and more and more plugins will stop supporting it. Ideally switch before then, so that you decide the timing yourself.

Can I see the status of my version in the control panel?

Yes. The control panel shows the status (Stable, Expiring soon, Expired) of the PHP version for each website. The table above shows the same.

Read about web hosting

Didn't find the answer?

Reply within 1 working day · Mon–Fri 8:00–17:00 CET