Changes between Version 2 and Version 4 of Ticket #59231
- Timestamp:
- 08/28/2023 11:50:45 PM (3 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #59231 – Description
v2 v4 115 115 In 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. 116 116 117 I'll open a separate ticket to allow for discussing this proposal in more detail and for patches. 117 Separate ticket to allow for discussing this proposal in more detail and for patches: https://core.trac.wordpress.org/ticket/59232 118 118 119 119 … … 137 137 All 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. 138 138 139 I'll open a separate ticket to allow for discussing this and the previously listed RFC in more detail and for patches. 139 Separate ticket to allow for discussing this and the previously listed RFC in more detail and for patches: https://core.trac.wordpress.org/ticket/59233 140 140 141 141 … … 175 175 We may want to consider introducing a `wp_json_decode()` function to ensure the use of `json_validate()` (when available). 176 176 This would then mirror the already existing [https://developer.wordpress.org/reference/functions/wp_json_encode/ `wp_json_encode()`] function. 177 178 See: https://core.trac.wordpress.org/ticket/59234 177 179 178 180