• Anonymous

    I finally managed to upgrade from 0.72 to something new. I picked the latest available nightly version, which was 20/2/2004
    Regular upgrade didn’t work, and creating a new database with fresh install didn’t give me an option to recover my old entries. I ended up doing the following to make it work:
    -I edited the wp-config-sample file with the info for the existing database. The prefix for the tables was ?b2? in my old version, so I changed “wp_” to “b2”
    -However, in the actual database, some tables had the prefix, and some did not. In phpmysql I selected the tables without prefix, I clicked the ?operations? tab, and chose ?rename table to? to manually edit those names to start with ?b2?, and keeping the rest of the name intact. (My existing database had the following tables: b2categories, b2comments, b2posts, b2users, linkcategories, links, optiongroup_options, optiongroups, options, optiontypes, optionvalues. After I changed the names, they ALL started with b2.)
    -Then I ran wp-admin/upgrade.php
    It gave me one error when I was done:
    SQL/DB Error:
    [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ?https://developer.apple.com/documentation/macos8/TextIntlSvcs/Te%5D
    INSERT INTO b2options (option_id, option_name, option_type, option_value, option_description, option_admin_level) VALUES (93, ?blog_charset?, 3, ?utf-8?, ?Your blog?s charset (here?s a list of possible charsets)?,
    -I ignored this, and tried to log in. wp-admin/login.php gave a 404, but wp-admin/post.php let me log in with my existing name and password. Yay.
    So, this works, but it’s ugly and messy because:
    -I have that one error that I blatantly ignored.
    -I don’t know which of the tables that I kept from my old version are actually used in the new version. I couldn’t run upgrade.php WITHOUT first changing the names. It gave me lots and lots of errors, all involving the fact that I didn’t have b2options, or b2links. That’s what gave me the idea to rename my existing tables to match those names. But I renamed ALL of them, and I now I don’t know if I’m actually USING all of them.
    -also ugly because I still have things called b2xxxx. I mean, I could have just used “wp_” as prefix, and renamed everything to wp_xxxx, since I was renaming anyway. (Tip for anyone trying this method: rename everything to “wp_” so it will be correct for any future upgrades.)
    So, anyway, this took me a few days, but I have my old entries, and I can post. I still need to get my old layouts and other pages back up though, so I’m going to close the site until I’m done.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Sushubh

    (@sushubh)

    the forum and the WP edit page do not consume curly quotes from Word and turn them into question marks ??

    shelleycat

    (@shelleycat)

    The reason /wp-admin/login.php gave a 404 is because the file is now called wp-login.php and located in the root wp directory ?? I remember having the same problem myself when upgrading, I think it was moved/renamed at some stage and I just didn’t notice. You get redirected to the correct place when you try to post anyway (useful feature that)
    All my tables are named with the b2 prefix. This doesn’t matter because you set it to whatever you want in the config file, it could be anything. I’ve upgraded wordpress a few times with these tables without any trouble. I actually have two wordpress installations running from that database, the second one uses the wp- prefix. Again, no problems with either. So I don’t actually think this is something wrong with your blog.
    I got a similar error too when I upgraded, except I forgot to keep it. I wish I had as then we could put in a proper error report for the developers. It doesn’t seem to affect any functionality though.
    (I know Eva knows this already, just thought it might be useful to someone else)

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Successful (but ugly) upgrade from 0.72 to nightly’ is closed to new replies.