[wp-trac] [WordPress Trac] #55603: PHP 8.2: address deprecation of the utf8_encode() and utf8_decode() functions
WordPress Trac
noreply at wordpress.org
Thu Feb 22 22:12:50 UTC 2024
#55603: PHP 8.2: address deprecation of the utf8_encode() and utf8_decode()
functions
--------------------------------------------+------------------------------
Reporter: jrf | Owner: hellofromTonya
Type: task (blessed) | Status: assigned
Priority: normal | Milestone: 6.5
Component: General | Version: 6.0
Severity: normal | Resolution:
Keywords: 2nd-opinion php82 dev-feedback | Focuses: coding-
| standards
--------------------------------------------+------------------------------
Comment (by ironprogrammer):
Replying to [comment:50 hellofromTonya]:
> Well, #47699 to require JSON extension showed a way forward when
[https://core.trac.wordpress.org/ticket/47699#comment:6 VaultPress helped
to collect the information]:
> >The good folks at VaultPress have run some checks across the sites they
monitor, and have found approximately 0.01% of PHP 5.6+ sites don't have
the JSON extension available.
>
> I wonder:
>
> Are they available to collect it again?
Unfortunately, after reaching out to the Jetpack VaultPress Backup
(formerly VaultPress) team, the plugin has changed such that they are no
longer able to provide this information.
> One other thing to note is that an error code specific to the scenario
where the JSON extension missing is returned, which allows the number of
sites to being blocked from an update to be tracked in .org's mission
control to gauge whether this deprecation ends up being problematic or not
(see [46560]).
Would it make sense to include an `mbstring`-specific error code like that
introduced with [46560]?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/55603#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list