1. The tables do change. I believe some redundancies have been removed, among other changes.
2. If you need to revert, and you have your mysqldump backup file, reverting to 1.22 would be a matter of dropping all your weblog’s tables and then restoring from the backup file. This is a straightforward procedure with mysql (I did it several times this weekend, for various reasons) and I assume it’s the same with phpmyadmin. IOW, as long as you have backups, you can go backward if you need to.
Honest– you have nothing to lose by upgrading. Just read through the steps and make sure you understand what you should be doing for each one. Most of the issues so far appear to be from skipping over part of one or another step.
Actually there is another issue I forgot to ask.
If I upgrade to 1.5 and everything runs just fine and people keep posting, so my database is filled with new posts etc. I’m making a backup of this every day for instance.
And let’s say after a week I’m not that happy with the result, because I can’t use my old theme for example. Keep in mind, this is just an example 🙂 So err, I decide to put my old 1.2.2 version back, with my old skin.
I could just put all wordpress files back on my webspace. But would it still be possible to put my LATEST backup (with the new posts in my 1.5 version) back? Keep in mind that this backup will contain the 1.5 table structure, but that I am running the 1.2.2 version again.
From the changes I’ve seen, I *think* it would be possible. Just restore the comments and post tables (I’d avoid creating any new categories until you’re sure, though) from the 1.5 backup into your 1.2 tables after they’re restored and the blog is working again.
Failing that, WP 1.2x had an RSS importer that could do the trick 🙂 Move your 1.5 blog to another location (and a new database, unless you change the table prefix in the 1.5 wp-config.php file and the table prefixes in your database), then use the 1.2 RSS importer to grab the posts and comments from it. It might create doubles, though – I’m not sure that it’ll detect duplicates, so you might need to remove all your posts and comments before doing the import.
It sounds a little confusing I guess, but in theory it should work.
hrmmm … sounds confusing indeed. I’ve expected something simple, like ‘Yes’ or ‘No, not possible’. Anyone knows this for sure?
Thanks anyway 🙂
–
Ow, and I DON’T have 2 MySql databases. So I can’t try thisone out. Otherwise I would have I guess.
You don’t need two MySQL databases. Simply upload to a new directory and chang the default $table_prefix to something like wp15_
You can run several instances that way and test your new version first before upgrading your production server.
— Navid.
That’s an option too. But is it possible to change the $table_prefix before you actually import those tables into you database? I don’t want them overwritten …
& thx 🙂
Yes it is. You change the value in the wp-config.php file.
