[wpmu-trac] [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:          
 Severity:  normal      |    Keywords:          
------------------------+---------------------------------------------------
 I finally ended up noticing that many of the blogs in my network had old
 database versions. I've been debugging this for a few hours and discovered
 something that might be causing a lot of upgrading problems.

 What I found was that within the upgrade page (wpmu-upgrade-site.php) in
 order to mass update the blogs, a web fetching class is used (Snoopy) to
 execute the upgrade.php script for all the blogs. Debugging showed that
 the upgrade script was not getting executed at all, and it was because
 snoopy was failing to connect to the same server it's executed from :).
 The problem lies where the snoopy class tries to connect to the full
 nonexistent domain name used in WPMU, so the host is something like
 "theblogname.thedomain.com". In my server setting, if i do nslookup or
 ping that domain name, it won't find it, while it will resolve the
 thedomain.com. Reason it can't resolve is because the server uses
 localhost to resolve DNS requests and my nameservers are hosted by my
 domain registrar with the wildcard setting. I'm not exactly sure how to
 fix this elegantly, but it can be fixed by modifying the Snoopy class to
 use the hostname when connecting. Also maybe some checking if the upgrade
 was actually successful, as it's currently misleading.

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