[wp-trac] [WordPress Trac] #23880: Minimum PHP version in Plugins
WordPress Trac
noreply at wordpress.org
Fri Aug 14 14:34:00 UTC 2015
#23880: Minimum PHP version in Plugins
-----------------------------+----------------------
Reporter: TJNowell | Owner:
Type: feature request | Status: closed
Priority: normal | Milestone:
Component: Plugins | Version:
Severity: normal | Resolution: wontfix
Keywords: | Focuses:
-----------------------------+----------------------
Comment (by alexander.rohmann):
My apologies for the wrong ticket. I looked for one but could only find
this. A maximum version is a good idea. That's standard in many places,
like PECL extensions.
Fully agree with @knutsp. If plugin develops are encouraged to deviate
from the "WordPress requirements" you end up with a mess of mismatched
versions. This dilution results in more things for the end-user to think
about. Over time it degrades the stability/reliability of WordPress as a
whole because you have no idea what to expect when activating a plugin.
I agree 100% that hosting compatibility is a concern, and in fact it is my
primary concern. The major setback here is lethargic outdated hosts - who
are never going to change until WordPress necessitates it.
So what if hosts are reluctant to update because of their own slew of
legacy application cliental? I've seen this point made a few times, and I
can't fathom why that is something we should be solving. I fail to see how
that falls on WordPress as a responsibility.
Considering the influence of WordPress, I certainly understand being
gracious - but at this point we're coddling them. Owners of non-WP legacy
PHP sites will at some point (soon) need to realize their mistake and pay
up to get a new system. Why should WordPress be hostage to other people's
failure?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/23880#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list