• This is based on a few bumps I had tonight. Thanks to the help from the Lizard and the Duck! ??
    NOTE: THIS IS AN UPGRADE FROM WP 0.72 to WP 1.0!
    Here’s what I did to get it going:
    1. I unzipped the archive on my local PC.
    2. I took the settings from my backed-up wp-config.php file and manually updated the wp-config-sample.php file.
    3. I deleted all of the WordPress files and folders on my web server AFTER MAKING A COMPLETE BACKUP OF EVERYTHING.
    4. I uploaded all of the new WordPress 1.o files and folders to my web server.
    5. I changed the name of wp-config-sample.php to wp-config.php.
    6. I pointed my browser to /wp-admin/upgrade.php and ran the script.
    7. I loaded up my blog on my browser, and logged in.
    I hope that this helps someone.
    Craig.

Viewing 15 replies - 16 through 30 (of 32 total)
  • Fatal error: Call to a member function on a non-object in /home/heather/public_html/wp/wp-admin/upgrade-functions.php on line 31
    Anyone have an idea why im getting this error message when i try and upgrade…

    @casedaling: I would make sure all the settings are correct (check with the wiki and the forum if you are unsure) and I would make sure you have correctly uploaded all of the WP 1.0 files.

    I tried upgrading from 0.72, but apparently the upgrade has failed. Can anybody say what has happened?
    https://bytewarrior.madoka.be/b2
    I ran the upgrade.php. My links are there, but no posts and I can’t login. I checked the MySQL database and everything is still there (unchanged). Any hints?

    A little bit more information about my update-problem …
    Apparently the update worked, because in the calendar, you can ‘see’ the posts (and the title of the post in the tooltip). But still, I can’t login, and my posts don’t appear.
    If I try to send my password by clicking on ‘lost password’, it can’t find my account (although my account still exists in the DB.)
    Another problem: in the titlebar of my browser (Firebird) appears this after the ‘official’ title:
    <div>SQL/DB Error:<br>[<span>You have an error in your SQL sysntax ” at line 1<
    I have tried to install the latest nightly build, but it still gives the same errors and the same problem with the login/posts….

    i’m having some awful problems. The upgrade ‘seems’ to work fine…. but it doesn’t transfer my posts from the b2posts db to the new wp_posts db.
    I’m upgrading from 0.72 to 1.01

    mayne you and me both mister anonymous. you and me both…

    i was the last anonymous
    but yeaa… actually, when i try to run upgrade.php it says “It doesn’t look like you’ve installed WP yet. Try running install.php.” =\.. then yea, running install.php it works, then when i try to inport-b2.php… it ignores (or so it seems) the b2post db

    yep. my issues too. i am starting to get VERY frustrated

    It doesn’t transfer your posts from b2posts to wp_posts, it upgrades your b2posts file to WordPress. So if you were upgrading from b2 you should put “b2” as your database prefix in wp-config.php.

    *doh!*
    thank you so very much!
    /me feel so stupid

    allusion, if i do that, i get an problem with the links.
    “SQL/DB Error:
    [Table ‘tankgree_b2.b2linkcategories’ doesn’t exist]
    SELECT cat_id, cat_name, auto_toggle FROM b2linkcategories ORDER BY cat_id”

    Ok I am having this problem. I have not lost any post but they are not being shown. and looking at the structure of the new tables created and the old b2posts table, they are different. It id not upgrade that table.
    ok I tried to upgrade but it did not recognise the old tables so it asked me to do an install. I did and then I tried the “upgrade.php” script. no difference…
    is there anything in that script that I could manually use to do what I need?

    Thanks!
    I finally succeeded in upgrading to 1.0.1
    Now the customization begins again.

    AH! After reading this thread I think I’m afraid to try to upgrade from .72 =(

Viewing 15 replies - 16 through 30 (of 32 total)
  • The topic ‘Upgrade from 0.72 to 1.0’ is closed to new replies.