This is a pretty challenging where I started: Migrating my blog platform Wordpress MU 1.0 to the latest version 2.6. We can affirm that it is truly on the horror and the moment after a few hours, there is still no effective despite many pages read on the forums. So, for my part, I first worked with symbolic links in linux to maintain a working version. My plans to install a test version on another server but it seems to me that Bind pose problems (I already galleys to the install the first time).

So we're working on live production, it is much more fun and stressful!

The principle is simple on-balance in separate directories, first of all the different versions starting with the MU 1.2.2 then 1.3.3, 1.5.1 and 2.6 on his server with FTP or whatever you want . In each of updates, we will remove the theme folder to keep all the themes already added or changed.

be created for each of its version a home directory. it retains the basic version unaltered warm.

was therefore directory:

• plateformeblog.sav /
• 1.2.2 / [empty folder]
• 1.3.3 / [empty folder]
• 1.5.1 / [empty folder]
• 2.6 / [empty folder]

We have finally symlink which we configure our Apache server:
@ Plateformeblog /

So by how they position themselves to pass the version 1.2.2 in the directory of the 1.0: plateformeblog.sav / and we launch the following command cp-rf * ../1.2.2

Then we went to the directory where you extracted the first update and it launches a cp-rf * ../1.2.2 and crushes and all new files with old ones. Then we re-point with ln-s 1.2.2 plateformeblog. And this is the 1.2.2 is now enabled. But it has more categories for blogs posted! and encoding is UTF-8 transform.

And there is one party that remains rather difficult since we must safeguard its home base in latin1. This produces a file. Sql which we will implement several changes at least for my part because the tutorial followed unfortunately did not work as I hoped.

So I finally exported the database on windows ftp (bah vla manipulation) and then open the sql file over 500MB and automatically detected in iso menu editing and encoding in utf-8. Hopefully it is transparent, so it saves the file under a new name.

Bad luck on Windows, I tried to open this file with Notepad + +, PSPad, Notepad and not more than 500 MB! So I cut with a software Split windows in 4 of 123 MB file I then open that file in notepad, you make a cut all its contents before pasting it into notepad ansi returns this time. It sticks and it was right this time encoding for content ansi ansi. Phew. Then in notepad + +, it opens the new file that took care of registering under a new name and automatically, it must detect Ansi, but to change the encoding to utf8 and everything should be good. Finally, we group these four files into one and it is imported into the database.

UltraEdit Apparently, paying it seems would not have the constraints file size. And if you do not pellet export MySQL, you will not have this kind of inconvenience.

The problem comes from three new tables inserted to manage the taxonomy: http://trac.mu.wordpress.org/browser/trunk/wp-content/mu-plugins?rev=1141

It takes the same principle for version 1.3.3 by copying the 1.2.2 cp-rf * ../1.3.3 and you go to the directory to update and relaunch it this command. it removes it and recreate the symbolic link and this time a small error should appear if the files are still in the repertoire of mu-pluggins.

Blogging with 1500, the backup is already difficult. Many tables are not locked and some downright corrupt. It was therefore necessary to repair the database and export it.

It uses the same procedure without any constraints to migrate to the 1.5 to 2.6 and the latter especially are not going directly to higher versions because they do not work.

Finally, for each transition, remember to update your database that is more or less long depending on the number of blogs. One last tip for this update is well read the documentation on the official website: http://codex.wordpress.org/Upgrading_WPMU

Post This regroup in the future, following my updates. In all cases, a good thing to remember is not to grill the steps and options.

In case of migration issues, please contact me.