[wp-trac] [WordPress Trac] #14393: Maintenance mode overkill. Please refine usage of it

WordPress Trac wp-trac at lists.automattic.com
Sat Jul 24 05:58:38 UTC 2010

#14393: Maintenance mode overkill. Please refine usage of it
 Reporter:  bike             |       Owner:                  
     Type:  feature request  |      Status:  new             
 Priority:  normal           |   Milestone:  3.1             
Component:  Upgrade/Install  |     Version:                  
 Severity:  normal           |    Keywords:  Maintenance mode

Comment(by dd32):

 > That doesn't mean you can avoid .maintenance however... There's no way
 really of knowing whether a plugin is activated at least somewhere without
 querying every site. So I'm thinking we'll just have to live with
 is_multisite() ||.

 What i was thinking of, was something along the lines of adding to the
 .maintenance file:

 $type = 'plugin' || 'theme';
 $items = array('my_super_plugin/plugin.php') || array('twentyten');

 and then
 if ( $type = 'plugin' || 'theme' )
     if ( $item is active on current requested site )
        include maintenance message;

 ie. shift the most part of the site checking to the individual sites
 themselves, For core upgrades, you'd just die straight up obviously.

 Just putting it as a possibility as an alternative to taking down
 everyones site for a upgrade which affects only a subset of sites. That
 being said, the maintenance mode should only exist for a brief
 interuption, and administrators need to be aware of that.. So planning
 upgrades around maintenance periods and/or handling upgrades a different
 way would be in their best interests regardless.

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

More information about the wp-trac mailing list