Wordpress upgrade

Well, I’ve upgraded my Wordpress and it seems to be working. I went from version 1.5.2 to version 2.2.1, so I skipped several versions. But I’ve always felt that knowing which versions to skip is the key to minimizing computer hassles. Well, not knowing; guessing, really.

The upgrade was really smooth. I continue to be impressed with Wordpress’s approach to deployment and upgrades. For example, I’ve customized the hell out of many things in this theme, and I did nothing to move those customizations forward. Apparently version 2.2.1 still works with the version of the “Vanilla Mist” theme I installed two years ago, and everything just seems to work.

The really big question now is whether this ugprade has corrected that error everyone has been getting after posting comments. Can’t wait to find out …

This entry was posted on Friday, July 20th, 2007 at 7:53 pm. You can subscribe to comments on this post through its RSS feed.

9 comments posted:

  1. The first test comment in version 2.2.1.

  2. And I didn’t get an error when I posted it!

    Let me know if anyone sees any problems with the upgrade. And now I must give our bandwidth back to Megan, who has patiently stayed out of Second Life for the last 20 minutes. Thanks, Dear!

  3. Hm … let’s see …

  4. I’m sad to report that I still get the 500 error. Everything seems to post just fine, and I am certainly capable of using my Back and Refresh buttons to see what I just posted, but I still seem to get the error.

  5. Hey, something doesn’t make sense here. It works fine for me now. Try hitting F5 to make sure everything’s refreshed and let me know what happens. Arrgggh.

  6. OK, I’m trying this one while completely logged out, just in case that makes a difference.

  7. OK, that’s it — if you’re logged in with admin rights, it works fine now, but logged out it’s still a problem.

    I’ve done some research and everything I can find points to plugins, but I deleted all my plugins during the upgrade so that’s not what’s happening. I’ll keep trying … ARRGGGH!

  8. OK, after trying about 20 different things based on what I’ve seen on various Wordpress forums, I give up for now. And Wordpress’s support is offline until Monday. I’ll try them then.

    It’s funny, I found several references to Wordpress blogs that started doing 500 errors on every comment all of a sudden, but none of those specific fixes worked. Some were changes to the .htaccess file, and others where bizarre things like editing and saving a post, with rave thank-yous for the fix, but none of them worked for me. Sigh.

  9. Why not give us all admin rights? ;)

    Seriously, don’t do that. If you think Megan dresses you up funny in Second Life, just think of how many of us Photoshop geeks read your blog and how many photos you have (I’m thinking monkeys and typewriters).

Have your say

Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.