Wasting time…

I don’t know where Saturday went… Well, I do, really. Spent all day updating to the newest (stable) release of WordPress. Version 2.8 can be found here.

I will admit that while the blog doesn’t look like much (would probably be more interesting if I ever had something to say) but it does allow me to waste time and play. There is something about the challenge of “getting it to work.”

The upgrade didn’t go smoothly (of course, my luck.) So much for their “5 minute install” or even easier “upgrade.” Sure I backed up my files and database. That was the easy part. It was just as easy to get rid of the old version and copy the new version in it’s place. And that, my friends, is where it stopped. As well as did the blog itself.

I tried to open the page and was met with a blank white page, with no errors. Cleared my cache, and all the other standard things, and found it was just plain broken. Thank goodness I had copied the entire “blog” directory, not just the content.

Put it all back the way it was, and version 2.7 worked fine, with no issues. So I decided to try again (after reading lots of helpful suggestions on the many forums and web sites around the ‘net.)

The second time, I took a more methodical approach. Well, it was the same approach, I just paid better attention to what I was doing.

It did work better the second time, I got the prompt to update my database, and all was set. Except… the plugins. I had five that indicated there were updates. The auto update just simply doesn’t work, whether it be the blog (WordPress) software itself, or the plugins. (Did you notice the seemingly manual installation referenced above???)

So I proceeded to update three of the five plugins, manually of course. However, the Cronless Postie still says it needs an update, but I do have the latest installed. The flash clock needs updated, and I hope that will fix the issue where it doesn’t display in FireFox. But I need to make sure I don’t lose my Sub in the process.

However, I am stumped (and the issue that “wasted” all of Saturday) by the fact that I can’t get WP-Cache to function. It was totally hosed during the upgrade. Had all sorts of permission errors, and after hours of searching and gnashing teeth, I found what seems to be an answer that works for me here, on the Omninoggin site. That wasn’t the way it was originally set up, but that’s the way it installs and runs now.

I say “runs” but it doesn’t cache. That’s the whole point, and after more attempts, I’ve finally decided to try and find something else. So, on a sunny Sunday, here I go… (But, I DO have to cut the grass today at some point!)