[wp-trac] [WordPress Trac] #23880: Minimum PHP version in Plugins

[WordPress Trac]

#23880: Minimum PHP version in Plugins
-----------------------------+-----------------------
 Reporter:  TJNowell         |       Owner:
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  Plugins          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+-----------------------
Changes (by seancjones):

 * status:  closed => reopened
 * resolution:  wontfix =>


Comment:

 I'd really like to revive this ticket. (I apologize if just reopening it
 is considered poor form. I know it's probably better than launching a new
 ticket).

 I am NOT trying to discuss #33381 here. That is a PHP upgrade for core.
 This is an optional tag that can be used to help filter plugins and, as I
 hope to successfully argue, improve user experience AND developer
 experience, in an age where new installs have to jump through insane hoops
 to install PHP 5.2.9.

 I'd like to see this implemented for the following key reasons:

 - The vast majority of users are now on versions later than PHP 5.2.9
 - A good chunk of plugins are writing code that is not compatible with PHP
 5.2.9.
 - As we continue to diverge, plugin developers will increasingly forget
 what is PHP 5.2.9 compatible. For example, anonymous functions are
 incredibly convenient.
 - It is fair to highlight the experience of the user over the developer.
 Neglecting this makes the user's experience worse at the expense of the
 developer. This is a lose-lose proposition.
 - There is some precedent, as stale plugins that have not received updates
 for a long time are not searchable on the wordpress plugin page. Why
 should a plugin with a PHP version that is too high be easy to download?
 - It does not require an upgrade to PHP's core version.
 - It helps to shift the blame from users to hosts. If a user complains
 that they can't download a plugin, and they received a notice that it was
 because their PHP version is too low, developers don't get bothered, users
 don't get confused, and hosts get rightfully pestered by the people who
 are paying them, upping the ante for an upgrade.

 This helps to bridge the gap between #33381 which may not happen for a
 long time, and what we have now. It does not force anything on core
 features, but it does provide a mechanism to lean on hosts by giving them
 a very present economic reason to do it. If a host isn't offering good
 service, ditch them and go elsewhere!


 How?

 My idea is to have this work similar to hiding plugins that have not seen
 updates for a long time, these plugins could instead have a disabled
 submit button, with a note that the plugin is incompatible with your
 WordPress install, and a link to a help page on WordPress.org, for how to
 address the problem.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/23880#comment:63>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform