Upgrade WordPress MU 2.7 to WP Multisite using DNS manilupation

Go login to that subsite. It’s probably the most recent one, not the first one, as it goes backwards through the list.

Alternatively, have a look at the URL it makes when it steps thru the blogs. You can change the number to manipulate it into starting at another blog.

Thanks Andrea,
I think another scenario if possible upgrade it directly using background process. As i have really big database, just to make sure its not timeout when the “upgrade button” clicked.

First thing i thinking about manipulate DNS for simplify the migration.
Then another question comes up how about handle the timeout. I’m working remote positively.

Btw, I’m using Nginx. And not problem about this setting :).. glad to see it’s work. I will post my setting latter in the ngix section later.

As i have really big database, just to make sure its not timeout when the “upgrade button” clicked.

it only steps thru 5 or 10 at a time. not the whole thing.

From my notes:

force update blogs to continue
/ms-upgrade-network.php?action=upgrade&n=80 <— change last number

Okay, then i decide to use live development..
Running smoothly with duplicate old grandpa there.. ??

Before this thread closed-resolved, I’m still aware about the upgrade process..
I notice the upgrade use javascript to force the browser, and it execute process step by step.

If possible to running the process of “UPGRADE NETWORK” using backend process? I mean using “screen”, or a closest server-node as a client (remote work).
Beside that way, i’m still figuring the upgrade process in database update perspective. Maybe try to manually run the process, outside Admin Area..

Well, it’s just came on my mind..a little bit nervous effect maybe, because i’m preparing a “big” multiuser migration.

Thanks for the tips&trick..

You can use the command line or a shell script to automate the backup. Using the URL Andrea posted, you’d do something like:

wget https://YOUR_DOMAIN.COM/ms-upgrade-network.php?action=upgrade&n=80

Change YOUR_DOMAIN.COM and the n=80 piece via a shell script and you should be good to go. There are probably cleaner ways to do it, but that’s an off the cuff suggestion.

And, obviously, if anything ever changed with the upgrade URL in WordPress, you’d have to keep updating your shell script. So this may not be a practical way to do it.

Thanks Andrea & Tim ..
I have on the track now.

First, all blogs in upgrade process doing some action to call a real DNS. Meanwhile, the etc/hosts in windows can’t handle wildcard/ “*”.
As long you can list down all your subdomain in etc/host, its not a problem. I tested it, and it’s worked..
But not for Multisite with thousand subdomains i think.

So, I found solution to manipulate DNS through a server, set up little DNS server to manipulate this.

Maybe the http.php do some action to call or check DNS, i dont know.

But now i’m on the right track and upgrading process.

Second, you can minimize the risk for timeout in upgrading process with a little temporary hack in http.php (some settings about request between http-req, curl, fsock etc.).
But if you not set the hack, its not problem at all. The countinues upgrading process helping much and much better :). Just like Andrea said.

So, it solved for now.
For a second, i just think about scalling and clustering process in WP Multisite… I hope there’s someone here bring it here ??

Terima Kasih (thank you)