[wp-trac] Re: [WordPress Trac] #6503: Random plugin structure should be deprecated

[WordPress Trac]

#6503: Random plugin structure should be deprecated
-------------------------------------+--------------------------------------
 Reporter:  robertaccettura          |        Owner:  anonymous
     Type:  defect                   |       Status:  new      
 Priority:  normal                   |    Milestone:  2.6      
Component:  General                  |      Version:  2.5      
 Severity:  minor                    |   Resolution:           
 Keywords:  plugin directory update  |  
-------------------------------------+--------------------------------------
Changes (by DD32):

  * keywords:  plugin, directory, update => plugin directory update

Comment:

 > (e.g. auto updates that do not distinguish which plugins are _not_
 checked....)
 There is a ticket elsewhere for the autoupdate and UI, but no ones done
 any work for a UI for it: #5117

 However, I'm not too sure on what the rest of the message is trying to
 say..

 > Mark -- I believe !WordPress's presumption that "of course" all plugins
 should go through WP Extend does a significant disservice to many plugin
 authors

 !WordPress "Encourages" that plugins are added to the !WordPress.org
 database, but obviously, Doesnt require it for plugin operations, but
 '''does''' require it for any plugin-related tasks such as auto-update or
 update notifications(unless the plugin takes care of that itself).

 '''All''' plugin authors are going to ultimately have to release plugins
 ''in the format which !WordPress uses''. - If !WordPress was to drop
 support for the current plugin system entirely(not gonna happen..) then
 plugin authors would then re-release plugins in a compatible format, Its
 the plugins which need to adhere to the way !WordPress works rather than
 !WordPress bending backwards to support old plugins or poorly coded
 plugins. (IMO)

 Files simply droped in the /plugins/ folder is ok, But its strongly
 recomended by me and others to put it in a folder, Simply so !WordPress
 knows what files are what, If its just a simple plugin, then feel free to
 put it straight in /plugins/ but be warned that the !WordPress plugin
 upgrade will put it into a folder.

 I dont think ignoring single-file plugins in /plugins/ is a good idea, its
 good for backwards compatibility and simple custom plugins, Overtime,
 !WordPress will probably sort them into folders as updates come out
 (assuming its on wordpress.org)

 (apologies for repeating myself, or some points not making total sense)

-- 
Ticket URL: <http://trac.wordpress.org/ticket/6503#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software