• Resolved tingarg

    (@tingarg)


    Hi,

    Yesterday in the wee hours of morning after dazedly feeding my 3-month-old and being unable to go back to sleep, I got the brilliant idea to upgrade my version of wordpress hosted on yahoo. I’d read about the auto upgrade plugin, that it worked on yahoo and dove right in…

    So, long story short, I completely hosed the upgrade. Now, I have my blog “saved” as a sql file in the format used by wordpress version 2.0.2 or something similar (whatever yahoo gave me) and I’d really, really not like to lose it as it contains over a year of stuff.

    My question: what is the best way to get this sql mass into the latest version of wordpress? In particular, I notice that the schema has changed across versions, so I need to understand how I can “mash” the old schema into a new db. Any ideas, suggestions, etc will be greatly appreciated. Thanks,

    Tito.

Viewing 4 replies - 1 through 4 (of 4 total)
  • whooami

    (@whooami)

    … I need to understand how I can “mash” the old schema into a new db.

    you cant.

    You have the dump, thats good.

    delete whats your on your site except for — SAVE your wp-config.php and your current theme, and the plugins.

    Upload the 2.0.2 files from a fresh zip

    Go into phpmyadmin and import that dump.

    Your blog will be back.

    ——

    Then, change to the default theme.
    Then, disable all your plugins.

    Then delete whats your on your site except for — SAVE your wp-config.php and your plugins.

    Then go download 2.1.3 and upload those files to your site, with the following exceptions:

    You do not need to worry about any of the js stuff inside wp-includes.

    They have no effect on the upgrade process

    You also dont need any images

    Just the core stuff …

    Then load wp-admin/upgrade.php in your browser

    Then take a quick peek at your source to make sure you are upgraded to 2.1.3

    Then delete whats your on your site except for — SAVE your wp-config.php and your plugins.

    Then go download 2.3.3 and upload those files to your site, with the following exceptions:

    You do not need to worry about any of the js stuff inside wp-includes.

    They have no effect on the upgrade process

    You also dont need any images

    Just upload the core stuff …

    Then load wp-admin/upgrade.php in your browser

    Then take a quick peek at your source to make sure you are upgraded to 2.3.3

    Then delete whats your on your site except for — SAVE your wp-config.php and your plugins.

    Then go download 2.6.3 and upload ALL of those files to your site. (Compare the new wp-config.sample.php to your old wp-config.php and make the necessary changes.)

    Then load wp-admin/upgrade.php in your browser

    Then youre done.

    I have done that all in less than 15 minutes on yahoo server. Of course, I’ve done a lot of upgrades. Once you know the routine, it’s very easy.

    PS: I left out the yahoo specific bits about having to change db permissions and what-not to do upgrades on Yahoo only because you didnt have any problem with the last one that pointed to that being necessary.

    What I’ve provided is full-proof (unless I typo’d and thats possible as I havent slept in quite a while). Youre version of WP wont play nice with a straight upgrade to 2.6.x

    Go the incremental route.

    Thread Starter tingarg

    (@tingarg)

    Whoa.

    That sounds involved, but I guess I can only thank you for such detailed and helpful instructions… Thank you!

    whooami

    (@whooami)

    heya Tito,

    Check your e-mail ??

    Thread Starter tingarg

    (@tingarg)

    As a follow-up for the benefit of the group, I want to share the resolution of this issue. The destruction I’d done to my blog was understated in my previous post. While I had mysql tables containing my old posts, I didn’t have a full, working mysql db. I expected to have to write a program to extract all my posts and categories and emit them into a format wordpress could ingest. I knew this would take a great deal of effort and would likely take a week or more given my unfamiliarity with wordpress.

    In desperation, I contacted whooami through her blog and asked if she’d help me. Did she ever – my blog was back up and running the following evening! She was very easy+pleasant to deal with, needed almost no help/info from me, and under-charged me grossly. She literally just fixed it. Now I’m on the latest+greatest version of wordpress.

    If you find yourself in a similar bind, you might try looking her up…

    Thank you, whooami!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘recovering blog from mysql sql file after failed upgrade’ is closed to new replies.