Failed upgrade 1.22 to 2.2.1

  • frankieh

    (@frankieh)


    16 years, 10 months ago

    Hi people,

    I’ve had a 1.22 install of wordpress in place for ages, decided it was time to upgrade, so I performed the following steps.

    1. backed up everything (thank god, 8mb of sql)
    2. overwrote old with new.
    3. ran upgrade.php

    The result was a blank blog, no errors, but no html output either. The admin pages all gave me an “insufficient permissions” message but I double checked and the permissions were fine.

    So, Then I tried wiping the old install altogether (except for the newly restored 1.22 database) reinstalled all the newest copies of everything and ran the upgrade.php again, and again I got a blank output and no access to the admin pages.

    Then to prove to myself that it was the upgrade that was failing, I created a new db, and updated the config file to match and installed to that one. Perfectly.

    So I have a working WordPress 2.2.1 install. I just can’t use it without losing 8MB posts. (in SQL format)

    Has anyone had any problems like this before? I’d love to make use of some of the newer features and protection, but not at the expense of our past posts.

    kindest regards

    Franki

Viewing 9 replies - 1 through 9 (of 9 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    16 years, 10 months ago

    Try upgrading in stages. Upgrade the database to a copy of 1.5 and then from there go to 2.21.

    http://wordpress.org/download/release-archive/

    moshu

    (@moshu)

    16 years, 10 months ago

    If it’s not too late…
    http://codex.wordpress.org/Upgrading_WordPress

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    16 years, 10 months ago

    Also, he said “1.22”.. Is that a WordPress version? Maybe he’s running WordPress MU?

    If you’re running WordPress MU, you should go to the forums for the mu versions..

    http://mu.wordpress.org/forums

    moshu

    (@moshu)

    16 years, 10 months ago

    Actually, it was 1.2.2.
    1.2 was mingus – followed by a few security upgrades, and the last one before 1.5 happened to be v1.2.2.

    Thread Starter frankieh

    (@frankieh)

    16 years, 10 months ago

    Hi again,

    Taking the earlier advice, (after making a copy of the DB elsewhere to play with) I’ve now upgraded the DB to 1.5. (after it upgrades (upgrade.php I mean) the browser says it may take a while, and then later comes up with “page cannot be found browser message”. When I try and run it again, it says the DB doesn’t need upgrading.

    Anyway, I’ve upgraded the db to 1.5, the next step will be
    to try for 2.2.

    One of my install attempts was to follow the link you just gave mr Mr Moshu. http://codex.wordpress.org/Upgrading_WordPress

    It still left me with a blank page. I don’t understand why I couldn’t see any error message in the error_log either.

    weird.

    I’ll let you know how I go.

    thanks

    Frank

    Thread Starter frankieh

    (@frankieh)

    16 years, 10 months ago

    OK I got 1.5 working, so I then went for 2.2 got it all installed and apparently upgraded but only partially successful. I can access the wp-admin fine, but when I call the main index.php, the require wp-blog-header.php line results in the page cannot be found problem (I know because if I comment it out I at least see test text i put in there.)

    So there is some setting somewhere in the old DB that even after conversion stops the process.

    Looking at the upgraded DB and the new 2.2 install DB, there are many differences. (for one the upgrade has 14 tables and the new has 10.)

    The table rows are also in different orders so i don’t know if that is an issue. I’m going to try and get them in the same format and see how I go.

    If anyone has any tips, I’d love to hear them.

    rgds

    Franki

    markmichon

    (@markmichon)

    16 years, 10 months ago

    I think the problem you might be having with your index is that WP has since moved to a theme-based system. No longer are you modifying the root index.php file. Make a backup of your index file, and make sure you copy over the one that comes with WP incase you haven’t done that.

    Thread Starter frankieh

    (@frankieh)

    16 years, 10 months ago

    wish it was that simple.. but no, the index.php file has always been without changes.

    by upgrading the db manually and exporting/importing I seem to be getting somewhere and it’ll be nice and clean also.

    rgds

    Frank

    Thread Starter frankieh

    (@frankieh)

    16 years, 10 months ago

    I got it sorted!

    After doing the whole DB changeover manually, I had the “you don’t have permission….” message when I tried to access the wp-admin pages.

    The solution I found was a script called force-upgrade.php
    by a Mark Jaquith. It added some permissions to the mysql db and off it all went.

    I now have our 1.22 wordpress upgraded to 2.22, but I must say that this is possibly the hardest upgrade I’ve ever done. 🙂

    rgds

    Franki

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Failed upgrade 1.22 to 2.2.1’ is closed to new replies.