[wp-trac] [WordPress Trac] #12317: Plugin Compatibility Missing for 2.9, 2.9.1, etc.

WordPress Trac wp-trac at lists.automattic.com
Tue Mar 2 06:18:23 UTC 2010


#12317: Plugin Compatibility Missing for 2.9, 2.9.1, etc.
---------------------------+------------------------------------------------
 Reporter:  miqrogroove    |       Owner:  mdawaffe          
     Type:  defect (bug)   |      Status:  assigned          
 Priority:  high           |   Milestone:  WordPress.org site
Component:  WordPress.org  |     Version:  2.9.2             
 Severity:  normal         |    Keywords:                    
---------------------------+------------------------------------------------

Comment(by miqrogroove):

 Replying to [comment:4 mdawaffe]:
 > Can you give some in-the-wild examples?

 I only use about a dozen plugins myself.  Half of them are self-authored.
 Among the others, the one I personally keep an eye on is qTranslate.
 Somewhere around plugin version 2.0 the author removed the deactivation
 code.  Instead, in the current version, it stays activated and cripples
 the post editor.  It also displays a message, "The qTranslate Editor has
 disabled itself because it hasn't been tested with your Wordpress version
 yet. This is done to prevent Wordpress from malfunctioning. You can
 reenable it by clicking here (may cause data loss! Use at own risk!). To
 remove this message permanently, please update qTranslate to the
 corresponding version."  In other words, qTranslate is still never
 compatible with new (or old) WordPress point releases.

 Displaying "Tested up to 2.9.2" for the wrong version in Extend was a
 disservice to users.  I don't understand the logic of making it "opt out".
 The purpose of Plugin Compatibility and the Tested Up To header is to help
 identify these types of problems, not sweep them under the rug.

 Here's an idea for authors who "don't have to edit their readme every time
 a minor release comes out."  Add support for a Tested up to value called
 "branch".  So, a plugin author could specify "2.9 branch" to indicate
 there are no problems anticipate with point releases, but the author has
 not yet checked 3.0 compatibility.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12317#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list