screwed up 2.0.1 upgrade–HELP!

  • richards1052

    (@richards1052)


    18 years, 2 months ago

    I’ve screwed up something in my upgrade to 2.0.1 from 2.0.

    I followed directions in the Codex for upgrade. When I got to Step 9 I tried to use the Upgrade program and got an error indicating I hadn’t renamed wp-config-sample.php to wp-config.php. I did that but when I tried running the script in my browser I got another error which indicated I hadn’t used the proper username/password/database name settings within the file. So I filled that info in & saved the file.

    When I next ran the script, I got the following errors:

    Warning: Invalid argument supplied for foreach() in /home/richard2/domains/richardsilverstein.com/public_html/tikun_olam/wp-admin/upgrade-functions.php on line 56

    WordPress database error: [Unknown column ‘user_nickname’ in ‘field list’]
    SELECT ID, user_nickname, user_nicename FROM wp_users

    Warning: Invalid argument supplied for foreach() in /home/richard2/domains/richardsilverstein.com/public_html/tikun_olam/wp-admin/upgrade-functions.php on line 114

    Warning: Invalid argument supplied for foreach() in /home/richard2/domains/richardsilverstein.com/public_html/tikun_olam/wp-admin/upgrade-functions.php on line 122

    Warning: Invalid argument supplied for foreach() in /home/richard2/domains/richardsilverstein.com/public_html/tikun_olam/wp-admin/upgrade-functions.php on line 248

    Warning: Invalid argument supplied for foreach() in /home/richard2/domains/richardsilverstein.com/public_html/tikun_olam/wp-admin/upgrade-functions.php on line 298

    Now I can’t access my blog internally or externally. I’d welcome any ideas or suggestions about what I might be doing wrong. Perhaps I used the wrong database/username/password info in the wp-config.php file?

    Another thing…as I ftp’ed the upgrade files to my server Symantec claims it detected a worm within the installation files. Could this have screwed up my installation?

    I’m hoping I haven’t done anything majorly wrong & perhaps changing a setting will fix this (I’m hoping that’s true…).

    <b>UPDATE</b>: I just ran the upgrade script again & for some inexplicable reason it worked & I’ve got my site back.

  • The topic ‘screwed up 2.0.1 upgrade–HELP!’ is closed to new replies.

Tags