WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 16 months ago

#19503 closed enhancement

Add major core version global for easier plugin/theme development — at Version 2

Reported by: johnjamesjacoby Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords: has-patch
Focuses: Cc:

Description (last modified by johnjamesjacoby)

Problem:

Plugin/theme authors cannot reliably use $wp_version when doing their own feature development without hitting a chicken-egg scenario.

Example:

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.

version_compare() is inadequate for this when used in conjunction with WordPress core's versioning scheme:

3.2.1 is greater than 3.2
3.3-RC2 is less than 3.3

Paradox:

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.

Proposed Solution:

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 (3)

johnjamesjacoby2 years ago

comment:1 johnjamesjacoby2 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

comment:2 johnjamesjacoby2 years ago

  • Description modified (diff)
Note: See TracTickets for help on using tickets.