[wp-trac] Re: [WordPress Trac] #6262: Automatic Plugin Upgrade could break new plugins that require special instructions for upgrading

[WordPress Trac]

#6262: Automatic Plugin Upgrade could break new plugins that require special
instructions for upgrading
--------------------------------------+-------------------------------------
 Reporter:  nerrad                    |        Owner:  anonymous
     Type:  defect                    |       Status:  new      
 Priority:  high                      |    Milestone:  2.5      
Component:  Administration            |      Version:  2.5      
 Severity:  major                     |   Resolution:           
 Keywords:  dev-feedback 2nd-opinion  |  
--------------------------------------+-------------------------------------
Comment (by markjaquith):

 Any plugin that doesn't reference its files correctly is already broken.
 Whether it is the plugin upgrade putting it in an unexpected path or
 merely a fastidious manual installer, it's still a bug with the plugin.

 Same with special upgrade routines that trigger on activation hooks...
 that's bad practice.  Activation/deactivation hooks are for
 initialization/cleanup, not upgrades.  The plugin should handle upgrades
 through some other method.

 Neither of these problems are unique to the auto-upgrader.  These are
 problems that people could easily have run into with manual
 installation/upgrade as well.

 DD32, why do we need to ask if a plugin should be re-activated after being
 moved?  Can't we assume that?

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