Atomictumor

Well, its been a while since I put an official State of the Tumor address on this thing for all the loyal ‘tumorites out there.

With my belly full of official ORHS Orchestra pancakes and sausage (yum) and some Of Montreal playing from the hi-fi, I’m prepared to deliver that update, so hide the kids, put Grandpa in the bed, and read on.

These are the facts on this first Saturday of March.

We interrupt those facts for about 10 minutes while I discover that the most recent upgrade of Wordpress I put on the page has been deemed ‘dangerous’, on account of terrorist attacks on the source code. I understand that Interpol and the Council of Foreign Relations’s Illuminati Squad (COFRIS) has been working hard on finding the perpetrators. I have been told to suggest that anybody who may or may not have upgraded Wordpress in the most recent weeks upgrade to 2.1.2, or, apparently, a comet will strike you.

Another update of Wordpress? Gee, how well will this one go? It was soooo successful last time.

I have applied the update, and now am magically finding that none of the pages are loading. YAY!

Seriously, kids, don’t upgrade Wordpress to 2.1. Just don’t. Yes, yes, all the kids are doing it. If all the kids were jumping off a damn bridge, would you do it?

Yes?

Well, me too. But thats beside the point.

As I type these words, I’m re-uploading all of the 2.1.2 Wordpress files, hoping that perhaps the FTP server at my host has maybe jumped off a bridge, and prevented the first upload from working. Ahh, uploading.

OK, five minutes later, 300 loud curses, and a sore table-bangin’ fist later, I’ve isolated that either Filezilla (my FTP program), or the FTP server, doesn’t like completing the upload jobs, and stopped at the files starting with G. Now, everybody loves a G (don’t be a playa hata), but this is irritating, and not exactly how I had in mind spending this time we had together. I mean, seriously.

Lets check in with the upload, already in progress…

OK, the home page is working, none of the links out from it are. Or the box. Grr. Grrr. Grrrr.

Closer examination indicates that the whole G epidemic has proliferated throughout the rest of the folder tree. Hmm. Wonder whats up with that? Could it be time to lose good ol’ trust Filezilla? But its the most zilla of the FTP clients. Hmm.

OK, so I’m doing it again from the official hosts’s Javascript FTP client, and wishing that a comet would hit me.

5 minutes later, no comet yet. However, it looks like the Javascript client froze up. Yay! Yay for me and Java!

AT and Java are best friends!

…

Jesus Tapdancing Christ. This is a freakin nightmare…
30 minutes later, we’re still in a similar boat. I try to upload, and the FTP server wigs out. It’s stealing my goats and chickens.  I put an update on the front page saying that its broke (dur), but still can’t get things working.

Time to take a break.  Cuppa joe, walk outside, find a midget to beat up.  Yes, thats what the situation calls for.

—

Came back in, and did some searching, found out that my wp-config file has some evil spaces thats making everything wig.  Oh yes, I do believe things have been fixed.

Lo, how things hath been fixed.

MORAL OF THE STORY KIDS:

Upgrading anything is for chumps.  Never, ever, ever, ever upgrade things.  Ever.

—

This is not at all what this post was supposed to be… the morning started out so well!

Oh my god, is it broke.
More to come.