Make WordPress Core

Opened 3 years ago

Closed 6 months ago

Last modified 2 months ago

#57109 closed defect (bug) (invalid)

WP 6.1.1 > PHP 8.0/8.1/8.2 Dev Note is missing

Reported by: mdxfr's profile mdxfr Owned by:
Milestone: Priority: normal
Severity: major Version: 6.1
Component: General Keywords: php82 close
Focuses: docs Cc:

Description

see https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/

Just add a post in the core make dev blog to clarify what PHP version WP 6.1 is compatible with, and link it to the handbook page.
Because PHP 7.4 is reaching EOL by 28 Nov 2022, some could get in a hurry in a few days... to find if WP runs ok against PHP 8.0/8.1/8.2

i ping desrosj because the 6.1.1 release date is very soon :-)

Change History (7)

This ticket was mentioned in Slack in #core by mdxfr. View the logs.


2 years ago

#2 @jrf
2 years ago

A dev note is in the works and is planned to be published around the same time as the general release of PHP 8.2.

#3 @hellofromTonya
2 years ago

  • Focuses docs added
  • Keywords needs-dev-note php82 added

Hello @mdxfr,

Welcome to WordPress Core Trac! Thank you for opening this ticket.

The plan is to publish a generic WP PHP dev note when PHP 8.2 is released. When? Currently, the 8.2 release date was rescheduled to December 8th.

Please note, the handbook was updated when WP 6.1.0 released. It shows compatibility for each PHP version. https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/

#4 @mdxfr
2 years ago

the question is more when the beta status will be raised for 8.0/8.1, since from 28th november those will be the only PHP versions with no EOL ;-)
Just to clarify to novices that WP is running well with 8.0/8.1, with only warnings.
and call the third parts (plugins/themes) to confirm 8.0+ compat.

#5 @desrosj
2 years ago

  • Keywords close added
  • Owner desrosj deleted

Removing myself as owner as it's not something I'm working on (or had any part in so far).

The compatibility page in the handbook has been updated, so not sure if this really needs to be left open. We don't typically track posts through Trac tickets unless there are also underlying changesets required on the ticket.

Adding a close suggestion.

#6 @karmatosed
6 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from assigned to closed

I agree with closing this as has been suggested by @desrosj. If however, others do want to reopen we can always do that. It does feel after the time has passed we can now move this on so I will do that today. Thank you everyone.

For now, I am going to close with a status of 'invalid' although it could be 'fixed' due to the handbook status.

#7 @johnbillion
2 months ago

  • Keywords needs-dev-note removed
Note: See TracTickets for help on using tickets.