Obviously not in order of importance.
I can’t stand automated phone support machines where I have to speak to answer questions. I hate how they have them setup so it’s like they’re actually talking to me. ‘Ok, I can help you with that’. Annoying. Yes, this is how I spent my Sunday morning.
First, my Tivo has been complaining about not having up-to-date program information, even though its been successfully connecting everyday. Normally I use the network connection, but I figured I’d try the phone line to see if that would magically work better. This is when I discovered that I have no dial tone (but the dsl still works, thankfully).
Here’s where I called BellSouth (the shiny new AT&T) and discovered that they don’t have Sunday live customer support hours. That’s awesome. Because shit doesn’t break on Sundays. So, I went through the automated thing answering all the questions, getting forwarded to other support places and their automated systems where I *might* have to re-enter my 10 digit phone number, just to find that there is something wrong with my line. Thanks. Estimated fix, tomorrow. I can live with that since I never use the land line anyway.
Next, I called Tivo to find out what was going on with my program info. They actually have live support on Sundays and it took almost no time to get through to an actual person. Tivo +1. The support lady had me go through and reset my cable lineup. This is the part of the original Tivo setup where you put in your zip code, cable provider, and they ask what you see on channel X and what you see on channel Y, etc. Apparently, if the cable company changes channel lineups it can mess up how Tivo gets program info. This makes sense because Comcast made changes to the channel lineup on March 01. So far, it seems to have worked because now my program lineup extends past 8:00 pm tonight. Tivo +2.
Conclusion: BellSouth, via the new AT&T, sucks. Tivo is awesome. Also, I don’t really like Comcast.
I like to make food. I like to eat food. I created a flickr set celebrating my love of making and eating foods. I will never create a set celebrating doing the dishes, because I hate that shit.
It seems that some malicious code was introduced into the WP 2.1.1 download in the last week or so. The dev blog’s got the news. It is recommended to upgrade to 2.1.2. Now!
I upgraded to the latest WordPress version tonight without too much of a struggle.
The only real issue I’ve seen so far is that there is a difference in the database tables when going from 2.0.x to 2.1.x. Gone is the wp_linkcategories table in favor of link categories being stored in the wp_categories table along with post categories. This broke my sidebar a little, which was an easy fix, and I imagine it might mess up my backup script some. Also, you shouldn’t update a 2.1.x db with a backup from the 2.0.x family. My local test blog can attest to the destructiveness of this action. If I had done some reading (and thinking) before I upgraded, I might have learned all this.
The one plugin I wrote that I actually use seems to work fine, so that’s good. Also, for the one other person that uses a plugin of mine: I’ll test it at some point. Promise.
Done.