So yesterday, when I was in the midst of my CSS-related rage (since fixed), I was cursing Ben and Mena in ways that would make sailors blush. And as a guy who works with sailors, trust me, I know.
But it was me, all me, that messed this up. So I offer this very public apology. I may even end up buying a license for this thing.
However, I have to say that I’m not sold yet. The last CMS I used (e107) was easier to set up and came with a lot more functionality by default. True, I had to wrestle it to the ground and beat it with a 2×4 to get non-tag soup out of it, but it had a lot to offer.
So for the time being, I’m giving MT a try. With some suggestions for plugins from the blogger I respect most, maybe I can get this thing working and looking good. Or at least maybe I can keep from making an ass of myself publicly any more.
UPDATE: D’oh. This blog is quickly becoming the “continuing story of a webgeek gone to the dogs…”. The problem, believe it or not is caused by a moose. A floppy moose.
It seems that my user-Content.css file thinks that some of the MT images are ads. Clearing out the ad-blocking stuff has MT working just fine. In fact, it’s probably my fault for not just using the default directory names. I’m so dumb.
Unfortunately this just brings up another difficult choice: Ad blocking or MT? Maybe with some luck I can turn images that point to mt.cgi back on.
As a last ditch effort, I go to my daughter’s computer and fire up IE. [I know friends don't let friend use IE, but it's the only browser that works with the sites she uses (their fault, not ours).] And whaddya know? It works.
So now I’m left in a quandary: Use the browser I love, or the CMS that everyone says is so wonderful?
Right now I’m leaning to blogging in one and browsing in the other, but it makes me feel like a real sell-out. I’m hoping this is just a freak occurrence, and some sort of upgrade will make all the pain go away.