I honestly don’t think that’s ever going to happen. The problem is that, when you have a really old version of WordPress, you have to make hell of a lot of database changes in order to upgrade to 3.4. Taken in small batches, these changes are fine. But try to roll them all together into one humongous upgrade that takes place over an extended time period (compared to a 1 version upgrade) and you are just asking for something to hiccup. End result: one seriously trashed database.
Thread Starter
pubwvj
(@pubwvj)
Yes, I understand that. What I’m suggesting is the WP team tackle this. Automate the process of making all those little upgrades to backup the old and then bring it up to the new version.
Saying you honestly don’t think it will happen isn’t helpful. I was simply giving feedback and making a suggestion.
Unwatched.
I’m not sure you understood the point I was trying to make. It’s not possible without a serious risk of destroying your database.
If you really have to, I’d suggest downloading the various releases available in the archives and applying them one-by-one until you get up to the current version.
As Esmi has said, your database is the biggest concern when you’re coming from a very old version, so be sure to creat backups of your files AND your database before each upgrade. That way if (in reality WHEN) a problem occurs, you’ll be able to revert back to the last stable version of your site.
If you really want to do this be prepared for it to take a long time to do. This is not something that you can rush at all.
There is also the other option of creating a new installation of the current software and doing a manual cut-and-paste of all of the old content into the new version. That would pretty much take the same time or less depending on how much content that you have.
