Make WordPress Core

Changes between Version 2 and Version 4 of Ticket #59231


Ignore:
Timestamp:
08/28/2023 11:50:45 PM (10 months ago)
Author:
jrf
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #59231 – Description

    v2 v4  
    115115In the rare case that the attribute, once added, would result in a fatal error, that would be fantastic, as that means we have actually found a bug in WP before it got into a stable release.
    116116
    117 I'll open a separate ticket to allow for discussing this proposal in more detail and for patches.
     117Separate ticket to allow for discussing this proposal in more detail and for patches: https://core.trac.wordpress.org/ticket/59232
    118118
    119119
     
    137137All 7 uses of `unserialize()` in WP Core should be reviewed and for the 6 uses outside of the `maybe_unserialize()` function, it should be reviewed whether they can/should switch to using `maybe_unserialize()` and/or whether they should get their own (improved) error handling.
    138138
    139 I'll open a separate ticket to allow for discussing this and the previously listed RFC in more detail and for patches.
     139Separate ticket to allow for discussing this and the previously listed RFC in more detail and for patches: https://core.trac.wordpress.org/ticket/59233
    140140
    141141
     
    175175We may want to consider introducing a `wp_json_decode()` function to ensure the use of `json_validate()` (when available).
    176176This would then mirror the already existing [https://developer.wordpress.org/reference/functions/wp_json_encode/ `wp_json_encode()`] function.
     177
     178See: https://core.trac.wordpress.org/ticket/59234
    177179
    178180