Tag Archives: TypePad

Moving on up, to WordPress

Well, after fighting all day to get back into the blog’s working system, I have decided to make the big switch. Lord knows what it will do to the layout, not to mention the content. I expect it will be a bear. We shall see.

The problem is that Yahoo, the host, and Movable Type, the blog software, parted ways earlier this month, which meant that Yahoo would no longer support MT. I ignored it, figuring I could go my merry way with MT. Then I axed TypePad as the comment vetter and, suddenly, I couldn’t get back into MT to work my magic. Come to find out that TP owns MT. Good grief, how did I miss that? TP said they couldn’t help. MT tried to pass the buck to Yahoo. I kept pressing MT. It took six hours but they finally found a solution. I’ll be making the switch as soon as I can. More on that when it’s ready to go down.

Your comments

I’ve discovered that you have to log in twice to get through the Typepad comment system here before it will recognize you. The first time it rejects you. Persist. You will get in on the second try. I have no idea why this is so. I considered moving the blog to WordPress with Scott Chaffin’s help, but decided I had better things to do than fiddle with a whole new system.

TypePad, what a joke

It’s on the fritz again. Can’t reply to comments or make any of my own. You probably can’t make any, either. Will it be sorted out? In due time, I’m sure. Oh, the suspense.

TypePad vs TypeKey

Another software quackware company change, another fouled up registration system. TypePad says I can use my old TypeKey registration i.d. and password. But it’s a lie. I cannot. Thus I can’t even get into my own comment system here. If you’re wondering why I haven’t replied to your comment, that’s why. Stay tuned.

UPDATE:  Still waiting, hours after my email request for "guidance," to get a response from the bozos. Finally heard back, but all they wanted was the error message content. Sent it off and… Still waiting.

MORE:  Two days later, on Wednesday, MovableType informs that: "The TypePad Connect team is working on a resolution for this in the application but I don’t yet have a timeline for that. We apologize for the issue." Still waiting…

AND: By Friday, the word was to wait a few days more: "We plan to have a resolution for this next week…" But by evening, it was fixed. Whew.