Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#16514 closed defect (bug) (fixed)

WordPress (still) displays wrong licensing info

Reported by: hakre Owned by: markjaquith
Milestone: 3.2 Priority: normal
Severity: minor Version: 3.1
Component: General Keywords: has-patch developer-feedback
Focuses: Cc:


I raised this already in #14685, strings for output to the user contain sort of wrong licensing information.

Compare: 14685-wording-add-ons.patch, this patch was before [17301], so it's not entirely correct any longer.

Just reporting before it gets lost.


Attachments (1)

16514.patch (6.0 KB) - added by hakre 5 years ago.
On Trunk / GPL v2+

Download all attachments as: .zip

Change History (7)

comment:1 follow-up: @nacin5 years ago

Wrong, or sort of wrong? I don't see a contradiction here.

comment:2 in reply to: ↑ 1 @hakre5 years ago

Replying to nacin:

Wrong, or sort of wrong? I don't see a contradiction here.


Wordpress Package Licensing:

  1. Current Wordpress 3.0.5 is GPL v2+.
  2. Older Wordpress Releases (3.0.4 and below) are GPL.

Excerpt of /wp-admin/plugin-install.php:

[...] are compatible with the WordPress GPL v2 license.[...]

@hakre5 years ago

On Trunk / GPL v2+

comment:3 @hakre5 years ago

  • Keywords has-patch added; needs-patch removed

comment:4 @jane4 years ago

  • Milestone changed from Awaiting Review to 3.2


comment:5 @markjaquith4 years ago

I think we should stay away from GPL version number specifics here. Some plugins are GPLv2-only. Some are GPLv2-or-later. Some are GPL (any version). Any of these is compatible with WordPress, which is what we want to convey.

comment:6 @markjaquith4 years ago

  • Owner set to markjaquith
  • Resolution set to fixed
  • Status changed from new to closed

In [18231]:

Be less specific about theme and plugin repo licenses (as they can vary in specifics). They are all compatible with the license WordPress uses, which is what matters. fixes #16514

Note: See TracTickets for help on using tickets.