[wp-meta] [Making WordPress.org] #2952: Plugin Directory: Allow minimum PHP version requirement

Making WordPress.org noreply at wordpress.org
Sat Jul 29 21:12:16 UTC 2017

#2952: Plugin Directory: Allow minimum PHP version requirement
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |

Comment (by rklrkl):

 I love this idea because when a plugin needs a newer version of PHP than
 core WordPess (currently 5.2.4 is the bare minimum), this is almost never
 mentioned on the plugin download page by the author (I complain about this
 on their support forums when I see this, but I generally get ignored).

 I haven't followed the full discussion of this, but if these two "obvious"
 ideas haven't been considered, you might want to throw them into the pot:

 1. Refuse to initially install a plugin/theme where the system doesn't
 meet the minimum PHP version requirements.

 2. Refuse to upgrade to a new version of a plugin/theme because the new
 version needs a newer PHP version than the one that's installed (this will
 stop auto-updates from breaking plugins/themes because of PHP versioning
 issues - this has happened to us several times). I don't know how easy
 this is though because you'd have to know the new version's PHP minimum
 requirements in advance (probably before the
 delete/deactivate/install/activate of the new version).

 BTW, I'm assuming that if a plugin/theme doesn't provide a minimum PHP
 version header, it will default to 5.2.4 (which will be wrong in quite a
 few cases as I've said - many plugin authors just look at the
 "recommended" version and not the minimum one!).

Ticket URL: <https://meta.trac.wordpress.org/ticket/2952#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list