Make WordPress Core

Opened 5 months ago

Closed 2 weeks ago

#62277 closed task (blessed) (wontfix)

PHP 8.x: various compatibility fixes for WordPress 6.8

Reported by: desrosj's profile desrosj Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords: php80 php81 php82 php83 php84 close
Focuses: php-compatibility Cc:

Description (last modified by desrosj)

Previously:

This ticket will be used as an "epic", allowing a variety of small patches each fixing a specific failure to be added to and committed against this ticket.

For patches addressing all instances of failures related to one specific PHP version (such as PHP 8.0, 8.1, or 8.2) change across the codebase, separate tickets should still be opened.

For an example of issues/patches with separate tickets, see:

  • #53299 PHP 8.1: Update is_serialized function to accept Enums
  • #53465 PHP 8.1.: the default value of the flags parameter for htmlentities() et all needs to be explicitly set

When opening a separate ticket, please tag it with the appropriate PHP version keyword so that these tickets can be easily found:

Change History (7)

#1 @desrosj
5 months ago

  • Keywords php80 php81 php82 php83 added

#2 @samiamnot
5 months ago

  • Focuses php-compatibility added

#3 @desrosj
4 months ago

  • Description modified (diff)
  • Keywords php84 added

#4 @desrosj
4 months ago

  • Description modified (diff)

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


4 weeks ago

#6 @desrosj
2 weeks ago

  • Description modified (diff)
  • Keywords close added

I'm thinking that this "epic" ticket type has run it's course and we can discontinue creating new ones going forward.

Since WP 6.3, there has only been one commit made to these tickets. Because there have been so few, we should encourage individual reports instead.

#7 @johnbillion
2 weeks ago

  • Milestone 6.8 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Agreed. No commits were made against this ticket for 6.8.

Note: See TracTickets for help on using tickets.