Upgrading to WordPress 2.0

Upgrade time: I’m deactivating plugins… things may look broken for a little bit, until I get it working right.

Just so you know. Don’t want to leave you out of the loop!

UPDATE:

I did it. My Archives broke, so I made a little fix for them until I can figure out what’s going on.

Otherwise everything seems to be working. Have to get used to the new Dashboard… it’s spiffier, that’s for certain. It looks like the WordPress guys still haven’t figured out Quicktags for Safari users, though. Bummer!

I’m hoping WordPress 2.0 won’t ping or trackback other blogs until the post actually publishes, a problem I’m having when I pre-publish posts. Otherwise, I’m very happy with WordPress and am glad to recommend it.

UPDATE:

Yowza, the new preview screen is INCREDIBLE. That was one thing that really bothered me about the old WordPress: the way the preview screen worked, like how blockquotes always showed up centered and with larger fonts than the rest of the post.

The new 2.0 is WYSIWYG, including header, sidebar and footer. Amazing!

9 Replies to “Upgrading to WordPress 2.0”

  1. My dear Ballpoint….I understand html, CSS and even Blogger, but…LOL…I have no idea what you just said. Are you speaking Swahili???? ROFLMAO1

  2. WP left me twitching. I couldn’t wrap my mind around it.

    Understand blogger, even livejournal.

    I do love what you’ve done with it. Shiny and spiffy good.

    Now for the archives to behave properly again. šŸ˜‰

  3. Bonnie C. & Kait, I think you would LOVE WordPress. (Once you stopped twitching, that is. Heh, Kait!)

    I’m doing it on my own webhost so it’s a little more technical than Blogger, but if you ever wanted more control over your blog (categories, themes, spam protection, etc.) you could transfer to Blogger’s biggest competition.

    Edited to add: Dennie, you and I posted at the same time!

  4. When I first upgrade to WordPress v2.0, I ran into many bugs, including one like your archive bug. After applying all of these changesets, I believe that most of the bugs have been squashed. So, if you have time, make a backup copy of your existing files (just in case), and apply those changesets. You will have to reset your permalink value in Options/Permalinks after you’re done with uploading the new files.

  5. James, define changesets. Are they like nightly builds? I’ll have to use upgrade.php after I install them, right? I just want to make sure I’ve got the procedure down.

    And dang! Now everybody knows I’m not the Swahili-speaking, mind-wrapping geek I made myself out to be, because I don’t know what a changeset is. Thanks a lot!

    No, wait—it’s OK because I can finally channel Dr. McCoy!

    Dammit, Jim, I’m a doctor, not a changeset tweaker. Dammit, Jim!
  6. I recommend that you follow this procedure:

    1. Open each of those changesets in a new tab from oldest to newest.

    2. Each changeset represents a small change made to a WordPress file, and since you will be replacing files, you want this to go as quickly as possible, so look through each tab and leave only the most recent changeset per file open. So, if there are three changests to the “functions.php” file, you want to make sure that only the most recent one is left open, since you will be replacing the entire file.

    3. In the changeset, hit the link(s) in the “Files:” field, you will see the file’s raw code displayed. Then, scroll to the bottom of the file page and option-click “Original Format”. Rinse, lather, repeat.

    4. Collect all of your newly downloaded replacement files in one folder (for organizational purposes), then launch your FTP (or SFTP) client and navigate to your WordPress installation.

    5. Now, delete the old files and replace them with the new files.

    6. Once that is done, run upgrade.php and re-set your permalinks.

    The whole process should take about fifteen minutes, depending on your connection speed.

    P.S. I forgot to mention that I had upgraded to Quicktag work-around in Safari for WP v2.0. You can find it under this FAQ listing.

Comments are closed.