Upgrade to WordPress 1.5 Strayhorn completed

Apologies if you were trying to read this site this morning and you had problems.

I was doing an upgrade of this site this morning from WordPress 1.5 Gamma (03/02/05) to WordPress 1.5 Strayhorn and I ran into a problem.

This blog is not in the WordPress folder but a folder called tom – hence tomandpilar.net/tom. WordPress is pointed at the tom folder and this doesn’t cause any problems. However, after upgrading I discovered that WordPRess was using the index.php file in the tom folder as opposed to the index.php file in the theme folder – which is what it should use in WordPress 1.5, and what it had been using in 1.5 Gamma.

After a bit of head scratching, re-reading Podz upgrade instructions, and the instructions on how to publish a blog in a different directory, I decided to try uploading the the wp-blog-header.php file from my backup.

I deleted the wp-blog-header.php from the remote site, uploaded the backup I made before I started from my own machine et voila, my blog returned to normal look and functionality once more.

This was a little scarey, though because I didn’t find mention of this potential issue anywhere in the WordPress Support Forums and the instructions for upgrading specifically state to delete the old wp-blog-header.php and replace it with the new one.

I’ll be interested to see if anyone else has this problem.

12 thoughts on “Upgrade to WordPress 1.5 Strayhorn completed”

  1. That’s a ‘feature’ of 1.5 – you see your own comments but no-one else does until the admin approves them – if the site moderates comments.

    I’m moderating still until I see how wp-HashCash works out. So far, so good.


  2. Thanks — I hadn’t seen your comment before I posted last. Very curious to see how wp-HashCash works out for you. I’m hoping to get some time this weekend to test it out, though I *may* upgrade first.

  3. If you are thinking of upgrading Diane, set aside some time, take your time, and read the upgrade docs carefully a couple of times before you do anything.

    Then back up everything – files and data. Keep copies locally as well as remotely so if you overwrite one backup, you can revert to the other.

    After that you should be fine.

  4. Tom, I came upon this link in my server logs, and realized I hadn’t responded. (Mea culpa!)

    At any rate, your recommendation is a good one; I think when I have some time I’ll try out 1.5 on a spare domain. I’ve quite gotten the idea from your WeblogToolsCollection link that there’s quite a bit different in 1.5 from earlier versions. Best not to be surprised on a live site!

  5. Absolutely Diane – proceed with caution, but do proceed and ultimately, you won’t regret the move!

  6. Thanks, Tom. (And thanks for the little favicon thing nex to my name!)

    Since I’ll be testing on a spare domain, I’ll be able to see all the new “wowie” features without threatening developedtraffic. But then, there’s that upgrade … 🙂

  7. Sure, or once you are happy with the spare domain, change the dns for developedtraffic to point to the spare domain, and copy the db into the blog there!

Comments are closed.