Post Content

Say, is there anyone out there who’s skilled in setting up WordPress and interpreting arcane SQL error messages and who’s been thinking, “I love that gosh darn Comics Curmudgeon — what can I do to make his life easier?” Well, here’s your chance. I’ve made a couple stabs at installing the SpamKarma plug-in, which everyone just raves and raves about as a killer of loathsome comment spam (I’ve had a bunch the last few days that featured the word “torture” a lot, so that’s another word that will get your comment put into a queue — sorry about that). But every time I activate it, posting a comment causes the blog to barf out a truly impressive SQL error message of some kind. If anyone would like to help me interpret said error message and possibly get SpamKarma working, e-mail me, please.

For those of you for whom the previous paragraph read like “Blah, blah, blah, blah, boring, stupid computer crap,” I apologize. Here, why not enjoy this image from yesterday’s post?

Ha, ha! Jeff has hairy arms!

Update: Upon further reflection I think I need a WordPress guru. WordPress in theory is supposed to hide all interactions with the SQL database from morons like myself. I can look at the error message and get the gist of what’s going on — there are some tables that WordPress and/or SpamKarma expect to find that they’re not finding, or that they’ve found and the permissions are wrong — but I have no idea why they haven’t been created and/or have the wrong permissions, and I’m really pretty sure that I shouldn’t be mucking around in the database directly, but rather fixing WordPress’s interaction with it (if possible). If you do know a WordPress guru, though, be sure to point them my way.

Yeah, apologies for the further dorkery. Look, the freaky Heat-Miser-hair dude from Gil Thorp has furry arms too!

(Thanks for Kevin Spencer for the cuttin’ ‘n’ pastin’.)