WordPress.org
Get WordPress

Make WordPress Core

Changes between Initial Version and Version 11 of Ticket #62061


Ignore:
Timestamp:
09/17/2024 08:14:24 PM (9 months ago)
Author:
jrf
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #62061

    • Property Keywords has-patch has-unit-tests added

  • Ticket #62061 – Description

    initial v11  
    106106=== GitHub Actions
    107107
    108 Add PHP 8.4 to the GitHub Actions `phpunit-tests.yml` configuration. [... GH PR #...] (won't pass until other PRs have been merged, see task list below)
     108Add PHP 8.4 to the GitHub Actions `phpunit-tests.yml` configuration. [https://github.com/WordPress/wordpress-develop/pull/7379 GH PR #7379] (won't pass until other PRs have been merged, see task list below)
    109109
    110110Notes:
    … …  
    122122This is a high impact deprecation, with ~880 of the top 2000 Packagist packages being affected by this deprecation.
    123123
    124 As the use of type declarations is relatively low in the WP codebase, this deprecation didn't hit WP that hard. Initial fixes for this deprecation were made in #60786, but some new ones have slipped in. [... GH PR #...]
     124As the use of type declarations is relatively low in the WP codebase, this deprecation didn't hit WP that hard. Initial fixes for this deprecation were made in #60786, but some new ones have slipped in. [https://github.com/WordPress/wordpress-develop/pull/7369 GH PR #7369]
    125125
    126126This deprecation also affected Requests (fixed in v2.0.11), Sodium Compat (fixed in 1.21.x) and SimplePie (PR open).
    … …  
    167167The mechanism of setting the callbacks with `xml_set_object()` has now been deprecated as of PHP 8.4, in favour of passing proper callables to the `xml_set_*_handler()` functions. This is also means that calling the `xml_set_object()` function is deprecated as well.
    168168
    169 This deprecation affects WordPress in a number of places. Patches for these issues are available. [... GH PR #...]
     169This deprecation affects WordPress in a number of places. Patches for these issues are available. [https://github.com/WordPress/wordpress-develop/pull/7370 GH PR #7370], [https://github.com/WordPress/wordpress-develop/pull/7371 GH PR #7371], [https://github.com/WordPress/wordpress-develop/pull/7372 GH PR #7372], [https://github.com/WordPress/wordpress-develop/pull/7373 GH PR #7373]
    170170
    171171''PHPCompatibility (`develop`) can detect code affected by this deprecation.''
    … …  
    183183
    184184This deprecation affects WordPress in a number of places, with `wp_trigger_error()` being the primary issue.
    185 Patches for these issues are available. [... GH PR #...]
     185Patches for these issues are available. [https://github.com/WordPress/wordpress-develop/pull/7375 GH PR #7375], [https://github.com/WordPress/wordpress-develop/pull/7376 GH PR #7376], [https://github.com/WordPress/wordpress-develop/pull/7377 GH PR #7377]
    186186
    187187> Note:
    … …  
    204204The alternative is to "manually" ping the database by sending a `DO 1` query (the cheapest possible SQL query).
    205205
    206 This issue affects the `wpdb` class in a minor way. Patch available. [... GH PR #...]
     206This issue affects the `wpdb` class in a minor way. Patch available. [https://github.com/WordPress/wordpress-develop/pull/7374 GH PR #7374]
    207207
    208208It is not expected that (properly coded) plugins or themes are affected by this change as those should all be using `$wpdb`.