PHP requirement always set to null for plugins

[diddledani]

The file class-wp-plugins-list-table.php line 764 (https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes/class-wp-plugins-list-table.php#L764) references a variable called $plugin. This variable is not defined anywhere in the function so the test will always return false, meaning that $requires_php will always be set to null:

$requires_php   = isset( $plugin['requires_php'] ) ? $plugin['requires_php'] : null;

This line was introduced in version 5.2.0

[afragen]

I think you’re correct. It should be $plugin_data['requires_php'].

I’ll step through the the code tomorrow and make certain.

Good pick up. Thanks.

[vaishalipanchal]

Patch.

[SergeyBiryukov]

This turned out to be not as straightforward as it seems :)

Background:

• [44937] introduced PHP compatibility check in WP_Plugins_List_Table::single_row()
• [45185] updated the check to use the new is_php_version_compatible() function.

Initially, I thought the check should be updated to use validate_plugin_requirements() to account for the data both from the plugin's main PHP file and readme.txt:

$compatible_php = ! is_wp_error( validate_plugin_requirements( $plugin_file ) );

However, upon a closer look, the purpose of the PHP compatibility check in this particular place is to disable the checkbox that could be used for bulk updating plugins, as some of the plugin updates might be incompatible.

The problem with this is that $plugin_data refers to the currently installed version of the plugin (which should already by compatible per the changes in #43986 and #43992), not the updated version that might have different requirements.

The information about the update is only available in wp_plugin_update_row(), which has its own PHP compatibility check per [44937].

So, unless I'm missing something, the current PHP compatibility check in WP_Plugins_List_Table::single_row() doesn't work as expected even with the proposed variable correction and should be removed. See 47835.2.diff​.

Disabling the checkbox for incompatible updates makes sense, but I don't see a clean way to do that at the moment.

[SergeyBiryukov]

The problem with this is that $plugin_data refers to the currently installed version of the plugin

Nevermind, I missed that $plugin_data is merged with the plugin API response​ earlier.

$plugin_data['RequiresPHP'] does indeed refer to the header from the currently installed plugin version, however $plugin_data['requires_php'] refers to the available update.

47835.diff​ is good to go.

[SergeyBiryukov]

In 45750:

Site Health: Use correct variable when checking PHP requirements for a plugin update in WP_Plugins_List_Table::single_row().

Props diddledan, sharaz, vaishalipanchal.
Fixes #47835.

[SergeyBiryukov]

Reopening for 5.2.3 consideration.

[JeffPaul]

Confirmed via @afragen in bugscrub (see Slack link above) that this has been tested.

[SergeyBiryukov]

In 45833:

Site Health: Use correct variable when checking PHP requirements for a plugin update in WP_Plugins_List_Table::single_row().

Props diddledan, sharaz, vaishalipanchal, afragen.
Merges [45750] to the 5.2 branch.
Fixes #47835.