[wp-trac] [WordPress Trac] #14915: Fix activation hook inconsistency

WordPress Trac wp-trac at lists.automattic.com
Sat Sep 25 23:33:27 UTC 2010

#14915: Fix activation hook inconsistency
 Reporter:  nacin         |       Owner:             
     Type:  defect (bug)  |      Status:  new        
 Priority:  normal        |   Milestone:  3.1        
Component:  Plugins       |     Version:  2.9        
 Severity:  normal        |    Keywords:  needs-patch

Comment(by dd32):

 > as we can't keep redirecting. Might need to hit wp-load with an Http
 request a bunch of times if it is more than one?

 I'm thinking that a HTTP request to loop back (with a nonce or something
 to bypass maintainence mode) for each active plugin as the final step of

 > And only kick on maintenance mode then also.
 I think it only kicks in right now if any of the plugin's you're upgrading
 are active. Maintainence mode is used so that when the plugin is only
 half-upgraded, a hit to the front end won't cause a "PHP Unexpected end of
 file" type error.

 Another thought just hit me. It's been "common" to utilise the activation
 handler to die-out to prevent the plugin being activated on blogs that do
 not meet the requirements, I cant think of a plugin off the top of my head
 which does this, But the old upgrade method had the ability that plugins
 could deactivate themselves upon upgrades if the new version wasn't
 compatible for some reason.

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

More information about the wp-trac mailing list