[wp-trac] Re: [WordPress Trac] #1175: Prioritize plugins

[WordPress Trac]

#1175: Prioritize plugins
----------------------------+-----------------------------------------------
 Reporter:  Skeltoac        |        Owner:  anonymous
     Type:  enhancement     |       Status:  reopened 
 Priority:  normal          |    Milestone:  2.1      
Component:  Administration  |      Version:  2.0      
 Severity:  normal          |   Resolution:           
 Keywords:  bg|needs-patch  |  
----------------------------+-----------------------------------------------
Changes (by majelbstoat):

  * resolution:  fixed =>
  * milestone:  => 2.1
  * version:  1.5 => 2.0
  * status:  closed => reopened

Comment:

 I still see this as an issue.  As was discussed on #768, there are
 problems with locales.  I have a multilingual plugin, Gengo, which sets
 the global locale based on the current post's language.  Other
 multilingual plugins exist and I'm sure they do the same.  I add a locale
 filter to set this.  However, many plugin authors choose to call
 plugin_load_textdomain() as soon as the file is included, rather than when
 first used.  (I'm probably guilty of this myself, too).  This means that
 any plugin which is loaded before Gengo will have the blog's default
 locale.

 The majority of the users of Gengo also install other localised plugins,
 because they want a consistent language across their pages.  I've had a
 number of reports of other plugins not being localised correctly because
 they are loaded before Gengo is.  My best response so far is "rename it
 x_plugin.php", which is far from ideal and which sometimes doesn't fix the
 problem.

 In general, the ability to specify a high priority for a plugin would
 allow for a closer integration with WordPress at the earliest possible
 opportunity, which would be very useful in a number of other areas, I'm
 sure.  We don't need a complex mechanism to make this all work - Ryan's
 suggestion in #768 of a Priority field in a plugins header would be
 enough.  And if you really wanted to, a Required field could be added as
 well.


 {{{
 /*
 Plugin Name: Parent Plugin
 Priority: 1
 ...
 */

 /*
 Plugin Name: Child Plugin
 Priority: 100
 Required: Parent Plugin, Hello Dolly
 ...
 */
 }}}


 I'm not too bothered about the Required: field to be honest, but I can see
 how it would be useful.  The Priority: field however, I consider, well, a
 priority :)  If this gets approval, I'm more than happy to draw up a
 patch.  Thoughts?

-- 
Ticket URL: <http://trac.wordpress.org/ticket/1175>
WordPress Trac <http://wordpress.org/>
WordPress blogging software