Getting the Comment Form to Display with Movable Type

I have to admit that one of the problems I have had with MovableType is that the comment form does not display on the single post pages. When you look at a post, you have to actually click on a link to get the form to pop up.

A quick google fixed that issue and I’ll copy it below.

What you have to do is edit your mt.js file from within your MT install and comment out the line that includes the following:


Since it’s Javascript two forward slashes at the start of the line will comment it out.

You don’t even have to do a rebuild except for that one file. Takes two seconds.

I hope this helps someone.

Yes, Jane, you are a Platformist


Wordpress ethics

WordPress ethics

Jane Wells asks if she’s a platformist.  Well, considering that her blog will only accept comments from those who have accounts [I won’t remind you that Matt Mullenweg censors accounts] and she didn’t bother to mention which Movable Type designer she slighted, I guess the answer to that question is yes.

edit: I’ve decided to turn off commenting on this post until she returns the favor.  I’m sure it’s just an oversight on her part and she’ll quickly fix the situation. (Can you tell I’m working on my sarcasm?)

Upgraded to Movable Type 4.21

Just a quick mention that I’ve upgraded to Movable Type 4.21. Please let me know if I broke anything.

I’ve already see one bug.  While you’re writing, the system will autosave posts for you as you write.  That’s cool and all that but after doing the save, it relocates the cursor to the beginning of the post content.  So, if you’re not paying attention, you’ll wind up with your writing in the wrong place.

That really bugs me. 🙁

edit: Reported here.

Damn Spam


What’s with all of the trackback spam lately?  That picture to the left there is the count for the last 20 hours or so since my last post.  Add 600 trackbacks that I’ve already deleted as well as the 303 comment spams from the other page and you get 2,886 of those little annoying buggers.  All caught by TypePad AntiSpam of course but then you have to go through and double check them.  At least I hope folks do that like I do.  Would hate to see something get caught by accident.

edit: OK, I found one issue that I fixed.  MT Auto Ban was not configured correctly.  That’s now been fixed and hopefully will be dropping bad IP addresses into the correct block list. (Just in the five minutes I’ve been looking at the plugin, I received 147 more trackbacks that got flagged as spam.) Maybe that’ll give me some breathing room.

How to fix “403 Throttled” errors for trackback pings in Movable Type

For a while now, I’ve been having problems with getting trackbacks sent out of this blog. (Mostly to WordPress blogs using Akismet I’ve noticed but that’s besides the point.) 

I did note a number of times I received a “403 Throttled” error within my activity logs.  A quick google search pulls up this article on Richard Green‘s site on How to fix “403 Throttled” errors for trackback pings in movable type.

Richard tells us to add in the settings OneHourMaxPings and OneDayMaxPings to your site’s /mt/mt-config.cgi file. (I note that as SixApart’s docs don’t actually say where to put those settings.) I’ve gone ahead and placed both lines in my config settings and saved the files.

…And watched the number of spam trackbacks go skyhigh.

Oh well.  At least my trackbacks are going out now.

Fixing the Comment Links

Some thing that has bothered me for quite some time is how Movable Type does it’s comment links. Instead of just a normal link to a website, it does this weird internal redirect. I’m sure the software does this to help prevent spam but with all of the protection built in, there’s really no need for something like that.

It’s easy to fix.  Here’s the code for the Comment Detail template.  You’ll find it under Design -> Templates -> Quickfilters -> Template Modules.

<div class="comment"<MTIfArchiveTypeEnabled archive_type="Individual"> id="comment-<$MTCommentID$>"</MTIfArchiveTypeEnabled>>
    <div class="inner">
        <div class="comment-header">
            <$MTCommentAuthorLink default_name="Anonymous" show_email="0"$> <MTIfNonEmpty tag="CommentAuthorIdentity"><$MTCommentAuthorIdentity$></MTIfNonEmpty> said:
        <div class="comment-content">
        <div class="comment-footer">
            <a href="#comment-<$MTCommentID$>" title="Permalink to this comment"><$MTCommentDate format="%x %X"$></a>

See the line up there with $MTCommentAuthorLink? That’s where the “Commenter bla-bla says:” get generated along with the link. All you have to do to get rid of the weird redirect link is add in no_redirect=”1″ to the line.

So the new line will look like this:

<$MTCommentAuthorLink default_name="Anonymous" show_email="0" no_redirect="1"$> <MTIfNonEmpty tag="CommentAuthorIdentity"><$MTCommentAuthorIdentity$></MTIfNonEmpty> said:

Why am I posting this? Because it’s missing from the docs. Rather annoying actually. Almost like reading WordPress’ codex once again. There used to be a plugin for this but it’s no longer needed.

Hopefully this will help someone else out. (And maybe get the docs edited to show this feature.)

Now I’m off to regenerate about 200 comments. 🙂

edit: Also considering that I don’t use nofollow on this blog, I think it’s important for folks to get credit for their comments.

reedit: You have to do the same to the Recent Comments widget.

Movable Type 4.1 gets released

Just a quick mention that Movable Type 4.1 was released. You can read about it here.  The upgrade went smoothly for me, once I remembered that I had to copy back in the config files.  The system kept thinking it was a new install and I kept canceling out since I knew that wasn’t right.