[wp-trac] Re: [WordPress Trac] #7487: Exclude files and folders from automatic plugin upgrade

[WordPress Trac]

#7487: Exclude files and folders from automatic plugin upgrade
-------------------------+--------------------------------------------------
 Reporter:  alexrabe     |        Owner:  anonymous
     Type:  enhancement  |       Status:  new      
 Priority:  low          |    Milestone:  2.7      
Component:  General      |      Version:  2.7      
 Severity:  normal       |   Resolution:           
 Keywords:               |  
-------------------------+--------------------------------------------------
Comment (by DD32):

 Since someone asked me to comment:
  * I do not support non-plugin files in the plugin folder, I see it as bad
 practice
  * I said in a previous ticket I'd look into putting a filter on it,
 However never got back to the ticket (and now cant find it); IMHO its more
 trouble than its worth for the small ammount of uses it'd receive - That
 and the trouble of upgrading non-auto-installed(ie;. non-upgraded, or non-
 plugin-install(2.7))) plugins having different directories than their
 slugs makes it a slightly messy issue
  * Yes, You might need to enter a custom path, However, Your plugin should
 only include other items on an init hook at which the DB is loaded, and
 any options are loaded, So store it there. Except in the case of Caching
 plugins, where you need to have a custom configuration file created
 anyway, So store it in a file in wp-content/ (WP-Cache 2 does that)
  * If you have non-plugin files which are !UserData, then store them in a
 user adta folder, Not your plugins data folder, Its not hard to tell users
 to upload their custom data to WP_CONTENT_DIR/GREF-Data/, and its not hard
 for your plugin to save them there in preference to your plugins folder

  * -1 overall, But if someone else feels like its a good idea and actually
 wants to spend their time to do it, Go ahead, But i'm not really
 interested in writing a patch i feel is rather useless to the vast
 majority, and only useful to a small handful of plugins (The email asked
 me if i'd write a patch up for it -- I dont think they've got anything to
 do with this ticket, so no finger pointing & theres my reasoning :))

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