Add major core version global for easier plugin/theme development
|Reported by:||johnjamesjacoby||Owned by:|
Description (last modified by johnjamesjacoby)
Plugin/theme authors cannot reliably use $wp_version when doing their own feature development without hitting a chicken-egg scenario.
I want a plugin to call function foo_32() for all major WordPress 3.2 branch versions.
I want a plugin to call function foo_33() for all major WordPress 3.3 branch versions.
3.2.1 is greater than 3.2
3.3-RC2 is less than 3.3
version_compare() is inadequate for this when used in conjunction with core's versioning scheme.
version_compare( '3.2', $wp_version ); -- Fails when 3.2.1 comes out
version_compare( '3.3', $wp_version ); -- Fails before 3.3 is released
Using version_compare() with any combination of operators yields the same result.
A new global: $wp_major_version
This would get bumped in trunk when development starts on the next major version. It provides plugin and theme authors the luxury of not needing to parse the major version out of $wp_version themselves. Patch attached.
Change History (11)
comment:1 @johnjamesjacoby — 4 years ago
- Summary changed from Add major core version global for easier plugin feature development to Add major core version global for easier plugin/theme development