#431 closed defect (bug) (invalid)
Compatible tag shows wrong version data
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | high | |
Component: | Plugin Directory | Keywords: | |
Cc: |
Description
Not sure how this happened, but I just discovered a plugin with the Compatible up to
tag set to 3.8.3, but all the plugins readmes (both in the stable tag, and trunk) are still on 3.8.1
I checked this against the plugin api as well which is also reporting 3.8.3 for the plugin.
Discovered on the qTranslate plugin; https://wordpress.org/plugins/qtranslate/
Change History (2)
#2
@
11 years ago
Additional: Sorry, I was confused about what was meant, I thought you were talking about the compatibility dropdown. Let me rephrase. :)
Forget the dropdown.
We maintain a "version equivalents" listing for versions of WordPress for this use. Anybody with "3.8", "3.8.1", or "3.8.2" will also be listed as compatible with 3.8.3 in the plugin listings. Same happens for 3.7 and other versions back to the 2.9 days. If we ever make major API changes in a point release, then there is the ability for the code to break that compatibility equivalent if needed.
Nevertheless, this is intentional. 3.8.2 and 3.8.3 were security and bugfix releases, and should not break compatibility for any plugin, and the directory knows that.
The compatible tag is listing the released versions of WordPress. It has nothing to do with what the plugin itself may or may not support in it's readme.txt files.
People may want to say it is compatible with 3.8.3 even if it has not been updated, after all.