[wp-trac] [WordPress Trac] #33381: Strategize the updating of minimum PHP version.

[WordPress Trac]

#33381: Strategize the updating of minimum PHP version.
-------------------------------------------------+-------------------------
 Reporter:  alexander.rohmann                    |       Owner:  jorbin
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Awaiting
Component:  General                              |  Review
 Severity:  normal                               |     Version:
 Keywords:  needs-codex dev-feedback 2nd-        |  Resolution:
  opinion                                        |     Focuses:
-------------------------------------------------+-------------------------

Comment (by seancjones):

 If I may propose what I think is a fairly conservative solution to throw
 into the mix in case this conversation spins out again (which I certainly
 hope it doesn't)...

 It's clear to me that developers can and will continue to update their
 minimum version of PHP. If the status quo continues, it is not impossible
 to imagine a universe where many plugins/themes are running PHP 5.5+ while
 WordPress itself does not acknowledge this change. This would leave users,
 who we are not expecting to know anything about WordPress and PHP,
 frustrated because many of the plugins they try to install do not work.

 A helpful step in the right direction, certainly for me as a developer -
 would be some ability to specify minimum PHP version compatibility.
 Composer allows this, and it would allow developers to code for newer
 version of PHP and make it immediately obvious to users that the plugin or
 even theme is not for their version, reducing confusion and frustration.
 Each disabled plugin could have a help link, "Why can't I use this?" which
 is an opportunity to teach users about PHP being EOL and to contact their
 administrator to upgrade their version of PHP. There could even be a
 sample script for users who didn't know what to say.

 This, coupled with a very clear warning on WordPress upgrade (that
 although WordPress is compatible with PHP 5.2.9 and later, users will not
 be able to access many plugins without updating to a current version of
 PHP), could help to increase PHP upgrades, without requiring it.

 Ultimately, WordPress is a mature project, and can probably get by with
 PHP 5.2-compatibility for a while yet. That doesn't mean that newer
 plugins are going to follow suit, and making it easy for users running
 outdated versions of PHP to spot it could be a minor solution if the major
 one can't be solved right now (which, again, I hope it can).

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