Making WordPress.org

Opened 8 months ago

Last modified 6 days ago

#7236 new defect (bug)

Requirements page update (MySQL and PHP)

Reported by: javiercasares's profile JavierCasares Owned by:
Milestone: Priority: high
Component: WordPress.org Site Keywords: has-patch
Cc:

Description

There are some changes needed to update in the WP.org Requirements page:

MySQL

MySQL 5.7 has their EOL on October 21, 2023. Having that in mind, we should not recommend using this version as is not having more releases, and the focus is only in MySQL 8.0.

Support for MacOS ended in January 2022, for Fedora ended in April 2020, for FreeBSD in October 2019.

So, we should change this string:

MySQL version 5.7 or greater OR MariaDB version 10.4 or greater.

to this one:

MySQL version 8.0 or greater OR MariaDB version 10.4 or greater.

PHP

Also, the PHP notice should be change, because WordPress 6.3 doesn't apply fully.

We should change:

Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.6.20+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities.

For this one:

Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 7.0+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities.

Change History (7)

This ticket was mentioned in Slack in #hosting by javier. View the logs.


8 months ago

This ticket was mentioned in Slack in #meta by javier. View the logs.


6 months ago

This ticket was mentioned in Slack in #hosting by javier. View the logs.


6 months ago

This ticket was mentioned in Slack in #hosting by javier. View the logs.


3 months ago

This ticket was mentioned in Slack in #hosting by crixu. View the logs.


3 months ago

This ticket was mentioned in PR #226 on WordPress/wordpress.org by @wildworks.


6 days ago
#7

  • Keywords has-patch added

Ticket: https://meta.trac.wordpress.org/ticket/7236

It is planned to update the Rosetta site to the new version in the following issue, and the new version is already enabled in some locales.

https://github.com/WordPress/wporg-main-2022/issues/266

My understanding is that if the new version is enabled, the Requirements page will load the following pattern:

https://github.com/WordPress/wporg-main-2022/blob/trunk/source/wp-content/themes/wporg-main-2022/patterns/about-requirements.php

The recommended version of this pattern is output via a shortcode and has been updated by the PRs below.

However, if a Rosetta site is not yet a new version, the page template below is loaded.

https://github.com/WordPress/wordpress.org/blob/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-requirements.php

Therefore, it is necessary to update the recommended version of MySQL/MariaDB even in locales where the new version has not yet been applied.

Below is the current Requirements page for the Japanese locale, which is not yet a new version.

https://github.com/WordPress/wordpress.org/assets/54422211/ea1f97fa-5483-4855-9d8a-c33e69efdf34

Note: See TracTickets for help on using tickets.