PHP 8.0 end of life: what next?

The status of PHP 8.0

PHPPHP is a programming language that builds your web pages on the computer that hosts your site, just before they reach the visitor. WordPress runs on it. 8.0 no longer receives updates from the PHP project. According to the PHP project, PHP 8.1 and older are outside regular support. The exceptional source patches for 7.4, 8.0 and 8.1 do not turn those branches back into regular releases.

Some distributions and LTS vendors supply their own fixes. Ask your host what has been applied to your installation rather than assuming that from the branch name alone.

Do not treat the number 8 in PHP 8.0 as evidence of current support. Give the full version in your request. Ask which supported branch is the target and how that choice will be checked.

What does this mean for your site?

Treat PHP support as a separate part of looking after your website. The question is not just which version appears on a screen, but who maintains the installation used by your site. Ask your host for the full installed version and the name of the party providing any fixes.

Keep that answer with the date of your check.

Separate the support status of the PHP branchA PHP version is a numbered edition of PHP, like 8.3. Each edition is looked after for a limited time, then gets security fixes only, then nothing. from the condition of your own website. A general support notice is not an investigation of your installation. Do not infer a specific breach from a version number alone.

Use the result to ask a clear maintenance question and identify the person who can answer it.

Route 1: update through your host

Ask your host which supported target versions are available for your website. Agree who will make the change and who will check the site afterward. A version selector in a hostingWeb hosting is the service that keeps your website's files on a computer that is always online, so visitors can open your site at any time. panel does not, on its own, tell you who owns those checks.

Prepare a list of things to test, such as sending a contact form, signing in and placing an order. Ask for a test on a copy and a usable backupA backup is a separate copy of your website's files and database, so you can bring the site back after a mistake, a hack or a failed update. before anyone changes the live setting. Agree on a way back if an important function does not work.

Choose this route when you or your web developer can take responsibility for those checks.

Route 2: ask us to help update PHP

Use the help form on this page if you want help managing the update. Include your website address, the PHP version you found and your host’s response. Explain which functions matter and whether an earlier update was attempted.

Do not include passwords in the form.

Ask for a proposal that names the target version, the testing arrangements and who does each part of the work. Our PHP update service page explains the service. Agree what belongs in the update and what needs a separate assessment.

Judge the result against a real visitor journey, for example opening the website, submitting an inquiry and receiving that inquiry.

Route 3: consider moving your website

If the current setup no longer suits what you need, discuss a move. First list what must remain: pages, addresses, forms, content and any connected services. Use that list to discuss a migration or a rebuild, rather than choosing a destination before the requirements are clear.

Compare the options against the same list. Who edits the content, who maintains the technical setup and how will you check the main functions after the move? See the migration and rebuild without PHP service pages for those routes.

A move is a separate project decision. While it is being prepared, agree who continues to maintain the current installation so that the existing question has a clear owner.

Turn the decision into an agreed next step

Keep the host’s answer, your chosen route and the responsible person together. When information is missing, ask a specific question: does the answer describe support from the PHP project or fixes supplied by a vendor? Which version will your site actually use?

Who will check that it works?

This page helps you choose a next step for one PHP branch. The general version guide helps you find your version. The support overview lists supported branches, while the PHP2Shell status page contains the wider facts and sources.

Follow those pages for background instead of treating this page as a replacement for the status overview.

Start with the Exposure Check

Start the Exposure Check

Ask for help using the form