[wp-trac] [WordPress Trac] #11138: WordPress deactivates plugin after upgrade

WordPress Trac wp-trac at lists.automattic.com
Wed Jan 27 20:12:10 UTC 2010

#11138: WordPress deactivates plugin after upgrade
 Reporter:  sirzooro      |       Owner:  westi                
     Type:  defect (bug)  |      Status:  new                  
 Priority:  normal        |   Milestone:  3.0                  
Component:  Plugins       |     Version:  2.8.5                
 Severity:  normal        |    Keywords:  needs-patch multisite

Comment(by wpmuguru):

 Replying to [comment:5 dd32]:
 > MultiSite probably wouldnt be affected the same way, As its the same
 wordpress install.
 > You'd need to be a site admin, and viewing the plugins page, and fetch
 the active plugins list as the other process was about to update it
 (Plugins are deactivated before singular upgrade) and then load the rest
 of the page after the other process deleted the files.

 In the current multisite terminology, dd32 is correct. This won't be a
 problem. Like the themes and plugins, the plugin/theme update data is
 shared/common across the network.

 In multisite in the old MU sense (what would be called multi networks
 under new terminology), this did occur as well. I believe the reason is
 that if the update check has not expired on the second network, the plugin
 page just puts out the info from the last update check. This may have been
 fixed in the 2.9 release.

Ticket URL: <http://core.trac.wordpress.org/ticket/11138#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list