[wp-trac] Re: [WordPress Trac] #7091: Allow plugins to be deleted via the WordPress admin interface / Group plugins by status

[WordPress Trac]

#7091: Allow plugins to be deleted via the WordPress admin interface / Group
plugins by status
-------------------------------------+--------------------------------------
 Reporter:  DD32                     |        Owner:  DD32    
     Type:  enhancement              |       Status:  assigned
 Priority:  normal                   |    Milestone:  2.6     
Component:  Administration           |      Version:  2.6     
 Severity:  normal                   |   Resolution:          
 Keywords:  has-patch needs-testing  |  
-------------------------------------+--------------------------------------
Comment (by stevish):

 Replying to [comment:10 scribblerguy]:
 > Exception Handling Issue: Multiple plugins in the same subfolder (sub-
 directory)

 What if we added a new stipulation to how plugins were created, that
 includes a file list? Perhaps the following format, in the plugin header:

 Associated files: dictionary.txt, langs/ (meaning the entire subdirectory
 named langs), user/user1.cfg

 Then in the delete/update functions, the following would be added:

 1. Check for file list
 2. If no file list exists, and plugin is in a subdirectory, show warning,
 including a list of files that will be deleted, then delete the entire
 subfolder
 3. If file list exists, delete only those files, and then perform a check
 that would delete any empty subfolders.

 This new stipulation could be considered another step in making sure
 plugins are compatible with version 2.6 (even though, for backwards
 compatibility, it wouldn't actually be *required* until 2.7 or 2.8, if
 ever).

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