[wp-meta] [Making WordPress.org] #4380: Plugin Directory: Be more flexible with the detected current major WP version
Making WordPress.org
noreply at wordpress.org
Wed Apr 10 17:32:14 UTC 2019
#4380: Plugin Directory: Be more flexible with the detected current major WP
version
------------------------------+--------------------
Reporter: Ipstenu | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone:
Component: Plugin Directory | Keywords:
------------------------------+--------------------
Looking at the code for get_current_major_wp_version, it does the
following checks:
1) Is there a define set
2) If not, what version is WP.org running
3) If that version is NOT a stable release (i.e. has a - in the name),
drop it down
The problem here is that value is checked when seeing if a plugin is
tested up to the current stable version, and some developers want to
update their code once they've tested against Beta releases. This is a
good practice, and should be encouraged, however as it stands today, their
plugins will throw an error if the version is higher.
This should be changed to factor in a +1 version or to allow for RCs... Or
be something we can edit without messing with the define
WP_CORE_LATEST_RELEASE
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/4380>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list