Make WordPress Core

Changes between Initial Version and Version 2 of Ticket #55603


Ignore:
Timestamp:
04/21/2022 09:12:28 PM (3 years ago)
Author:
jrf
Comment:

Replying to SergeyBiryukov:

For option 2, I think we'd need to also check the required PHP modules during installation, to avoid fatal errors. As far as I can tell, marking a module as required in Site Health displays a warning on existing sites if the module is unavailable, but does not block the installation for new sites.

Very good point! I always forget that those are two different lists of checks. I've added it to the action list.

Might also be a good time to improve the code re-usability in that regards (have one master list of requirements and recommendations, which both the requirements checker on installation/load + the Site Health component draw from).

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #55603 – Description

    initial v2  
    8989=== Action list for option 2
    9090
    91 - [ ] Change the MbString function from optional to required in the Site Health component.
     91- [ ] Make the MbString a requirement for installing WP/in the WP bootstrapping.
     92- [ ] Change the MbString extension from optional to required in the Site Health component.
    9293- [ ] Remove the current MbString related polyfills from the `compat.php` file.
    9394- [ ] Review the uses of the functions in WP Core and replace with more appropriate alternatives.