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

WordPress Trac noreply at wordpress.org
Mon Aug 17 13:27:51 UTC 2015

#33381: Strategize the updating of minimum PHP version.
 Reporter:  alexander.rohmann  |       Owner:
     Type:  enhancement        |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  General            |     Version:
 Severity:  normal             |  Resolution:  maybelater
 Keywords:                     |     Focuses:

Comment (by jdgrimes):

 Replying to [comment:22 markoheijnen]:
 > To me this is a users problem on the first place but that's to easy to
 say. If you say hosts should update then there is a problem since most
 hosts are already supporting 5.6 or 5.5. They simply can't just kill old
 versions as @jdgrimes said in one of his comments. Hosts also play the
 long game like WordPress does for the exact same reason: No breakage for
 their users.
 > So it's up to the user to update the PHP version of their account or
 sites (depending how the host work).  The big problem then is to make them
 understand why and how they can do the update themselves. When then the
 percentage of for example PHP 5.2 drops then it's easier for hosts and
 WordPress to kill it.

 I agree that at some point this might have to involve the user, but I
 still think that it is the host's place to get the user involved, not
 WordPress's. WordPress can't explain to the user how to update, because it
 can't be 100% sure that the user even can, or how they would do it. It
 varies from host to host. The host is in a much better place to encourage
 the user to upgrade, since they can actually explain how to do it, and
 will probably be the ones providing support if anything goes wrong. (Not
 to mention that the core team is adamant that they WordPress won't involve
 the user.)

 > What WordPress can and must do is to to scan the plugin/theme
 directories for plugins using things that will break when running PHP 5.5
 and later. So they can show to the outside that nothing can break when
 moving to the latest PHP version. I already have seen enough breakage that
 this can become a serious issue.

 I think this is a good point. The plugin repository is open source, of
 course, so anyone can create a scanner that will do this. Assuming that
 such a thing is possible, interested parties could build it themselves.

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

More information about the wp-trac mailing list