[wpmu-trac] Re: [WordPress MU Trac] #704: Database upgrade script can silently fail under certain conditions

[WordPress MU Trac]

#704: Database upgrade script can silently fail under certain conditions
------------------------+---------------------------------------------------
 Reporter:  MrBrian     |        Owner:  somebody
     Type:  defect      |       Status:  new     
 Priority:  low         |    Milestone:          
Component:  component1  |      Version:  2.7     
 Severity:  normal      |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by jamescollins):

  * version:  => 2.7

Comment:

 Replying to [comment:2 donncha]:
 > MU doesn't use Snoopy any more. This is a local configuration issue but
 it would be great to have a page listing the number of blogs that remain
 to be upgraded and/or list them. Anyone? The blog versions table is
 already there so it's easy enough to do.

 How about when loading wpmu-upgrade-site, the script queries the
 wp_blog_versions table for any entries that don't have a db_version that
 matches the $wp_db_version global variable.

 If there is at least one entry, then the option to upgrade site is
 enabled. If all db_versions are up to date, then a message is displayed
 and the button to upgrade the site is disabled.

 I could probably write a patch for this.

 Also, in wpmu-upgrad-site.php, when looping over each blog and performing
 the ugprade, is there a reason that the switch_to_blog() method isn't
 used? Currently a manual SELECT query on the blog's wp_x_options table is
 performed, but if switch_to_blog() is used, then we could use admin_url()
 instead of the manual SELECT.

-- 
Ticket URL: <http://trac.mu.wordpress.org/ticket/704#comment:3>
WordPress MU Trac <http://mu.wordpress.org/>
WordPress Multiuser