Blog under construction

I’m making more changes beyond playing with the theme this time around. For starters, I’m finally reposting the entries from Feb ’06 to Feb ’07. I saved them all onto my computer when I first wrote them on shawnbakken.com, but for some reason, I didn’t get that entire year’s worth of material on here.

Second, I’m going to play with the categories a little and add some tags to make it easier to surf through entries to find various topics. Even I don’t know the different kinds of posts that are in the Blatherings category and I’m the one who made it.

That may be the extent of the changes, but getting it all finished could take a while. Thankfully, I’m between classes at Augsburg, so it won’t be interfering with classwork. I’ve got the next couple days free to use at my discretion and this stuff has been on my plate for a while. Hope you enjoy the final result when it’s finished. (I hope I do, too.)

Testing, testing, 1-2-3…

I just installed a Twitter-based plugin that’ll send out a tweet every time I make a new blog entry on here. I fiddled with the options a little—I’m smart enough not to mess with coding anymore—and I’m wondering what the new tweets will look like. It’ll even show over on the right sidebar of the blog in the Twitter feed… who knows, maybe that’ll just fill up with a list of “Hey, look at this blog post!” Whether it does or not, it’s time to satisfy my curiosity and then fiddle with any options that need refiddling.

I had a little work done

A few days ago, the blog croaked. The reason? Me. But it was for a good cause, I swear!

Before said croakage, this sucker was ancient. WordPress has advanced to 3.0.5 (don’t ask how they figure out the decimals, ’cause I haven’t the slightest idea). Meanwhile, shawnbakken.net was somewhere in the early 2s. I thought that maybe because I wasn’t hosting the site, I didn’t have the administrative power to make the upgrade. I was wrong.

The problem was that the site was using an old web server. The person who is hosting this website switched web servers, which has much better customer service and has been much more effective overall. (I’ll get back to that in a minute.) Their instructions were to go to the site where I registered my blog, change the old web server information so it would connect to the new server, then wait until the new people upgraded the blog. It sounds complicated on paper… or on a computer screen, for that matter… but once I figured out where to go and which changes to make, it seemed fairly simple.

A few hours later, I went to look at the “Administrative Dashboard” and found a new login screen. I typed in my name and password to discover a whole type of dashboard: the type that you find on WordPress 3.0.5. Hell yeah…

As you may have noticed, the blog’s background and a bunch of other aesthetic things have changed with this new upgrade. Part of it is to make it all look prettier, although I’d like to find a picture of myself that I could use for the header instead of flowers or something (because I’m vain like that). Another part of it is because this background allows the use of “widgets”, which is how I added my Twitter feed to the right column of the screen. The old background didn’t have that option, but that didn’t stop me from trying to add them.

I surfed around WordPress’s help section and found something that referred to adding widgets to a site. It had instructions for adding a few lines of programming text to the “sidebar” and the “theme editor”. Assuming those changes worked, I could add some nifty new toys to the blog. As it turned out, the changes didn’t work. Or perhaps they would have worked if I’d done them correctly.

I copied and pasted all of the text from both pages into a Word file so I could undo the changes easily. However, that doesn’t do much good when you accidentally get rid of a line of programming from the theme editor and everything stops working. And I mean everything.

I couldn’t edit anything, I couldn’t get back to the Dashboard, I couldn’t even look at the blog. Whenever I tried, a notice came up about an error in the theme editor in line 3 (where I was making changes). It might as well have been a flashing neon sign on the screen saying, “Nice work, dumbass!” Honest to God, I had trouble getting to sleep last night because of it.

Thankfully, I got a message out to the Powers That Be (a.k.a., the new web server people who are much more awesome than the last ones) and they fixed the problem by the time I logged in today. *victory dance*

So the blog is back online for people to read and now has all sorts of little unnecessary toys that may never be used, but I thought they were neat. It shows the last five Twitter posts I made, you can “like” individual posts on Facebook, share the posts using different programs… there are some statistical toys that I can use on the Dashboard, too. Yay, toys!

So I spent a lot of time downloading and upgrading and playing with stuff this afternoon, but one thing I’m not going to do is mess with the editing tools. After all, if I screw up and the blog stops working again, how am I supposed to put a picture of myself up in the header?

Back online

Well, that wasn’t as ugly as I thought it would be. The person who’s running this site from her server switched to a new web host and everything was back to normal (or as normal as my blog gets) within an hour. It doesn’t look like anything was deleted during the hacking process, the person just messed with the main page and the administrative dashboard. Awesome.

On another note, I’m sure most of you have heard about the Metrodome collapse, which forced the Vikings/Giants games out of Minneapolis and into Detroit. It gets worse. The Vikes have another home game against Chicago on Monday night and they might be able to use the University of Minnesota’s football stadium, but in doing so, it would force the Bears to find an alternate site to prepare for the game. An alternate site like, oh, I don’t know, the Gophers’ practice football facility.

Remember how I was talking about all of the soccer games being cancelled last Sunday due to all the snow? They were supposed to be pushed ahead a week to Dec. 17th, the day before the Vikings game and likely a good day for the teams to practice. What I may not have mentioned was where our soccer league is playing this season: the Gophers’ practice football facility. Guess who’s gonna have priority and who’s probably gonna get screwed?

Hopefully, we can work something out. Mad Dogs are currently scheduled to play at 1:00 that afternoon, but “last minute changes are a possibility.” *sigh* I hope I can see my team play one more game this year. If not, that’ll be one more reason for me to hope that the Bears lose by a bajillion points. That’s right, I said “a bajillion”. No mercy for those who steal our soccer fields, bitches!

Mmmm, this website is hackalicious…

Okay, this is really weird. I went to the website itself and the “dashboard”—the opening screen for the site administrator—and both have been hacked. There’s a YouTube video on there about Muslim something something something… I haven’t taken the time to watch it, I’ve just been annoyed. Yeah, having a hacked website is definitely annoying.

But this is the weird part: I was able to circumvent said hacking by using Firefox’s history to go to one of the cached administration pages and it’s been working just fine (relatively speaking). I’ve been able to copy and paste all of my December entries that I hadn’t already saved on my laptop one by one—virus checker coming right up!—and navigate through the administrative stuff with no problems, but I just used a bookmark to get to the dashboard and there’s the hacked screen again.

I figure once I get this entry saved and “posted”—I’m sure it’ll appear somewhere eventually—I’ll try to poke around in here some more and see what I can see. Not that I’ve got a lot of know-how when it comes to WordPress, but what’s the worst I can do? Get the site doubly hacked? So it’s time for a little adventure. Keep your fingers crossed for me.