WordPress.org

Make WordPress Core

Changes between Initial Version and Version 74 of Ticket #40934


Ignore:
Timestamp:
03/08/2018 01:23:22 PM (2 years ago)
Author:
SergeyBiryukov
Comment:

Now that https://wordpress.org/support/upgrade-php/ is up, going to take a stab at implementing the mockups attached above.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #40934

    • Property Status changed from new to assigned
    • Property Focuses ui administration added
    • Property Component changed from Administration to Plugins
    • Property Milestone changed from 4.9 to 4.9.5
    • Property Owner set to joostdevalk
    • Property Type changed from enhancement to task (blessed)
  • Ticket #40934 – Description

    initial v74  
    11Not all plugins can work on PHP 5.2, like WordPress core currently does. Not all plugin developers ''want'' to support PHP 5.2, like core does. As a project, WordPress would like to move forward and have people on more recent PHP versions. One of the ways to reach that goal would be to show them that they cannot install a certain plugin or theme because their install does not meet the required criteria.
    22
    3 As such, I'm proposing to allow plugins and themes to have a minimum PHP version requirement. Not a maximum, just a minimum. This minimum version requirement should not mean that plugins should not be shown in the new plugins screen, for instance, instead, they should be shown but "disabled", with links to Wordpress.org pages explaining why, and how to upgrade their PHP.
     3As such, I'm proposing to allow plugins and themes to have a minimum PHP version requirement. Not a maximum, just a minimum. This minimum version requirement should not mean that plugins should not be shown in the new plugins screen, for instance, instead, they should be shown but "disabled", with links to WordPress.org pages explaining why, and how to upgrade their PHP.
    44
    55To do this, the following work would have to be done: