Learning Movable Type

I'm having a similar problem with my mt-tb.cgi trackback. Would this solution potentially apply also?

Thanks for this, Elise. I note that for my blog the script still gets called because my CGI scripts are not in the same exact location as my blog url. (One is at www.jackvinson.com and the other at blog.jackvinson.com.) Have you heard of a solution from the powers that be?

Hi Chris - I don't think this relates to trackback spam. TB spammers have been very active lately, however, and are doing mass floods of spam. See Trackback Spam for more ideas on how to fight it.

Hi Jack - The following was posted to the 6A ProNet list by Mark Carey, in response to a similar question:

My solution was to use PHP instead of perl to check for the cookie. My javascript looks like this:

if ('www.markcarey.com' != 'www.stanthecaddy.com') {
document.write('<script src="http://www.mark' +
'carey.com/cmtr_name_js.php"></script>');
} else {
commenter_name = getCookie('commenter_name');
}

(off topic: I broke up the URL to the script to prevent spiders from
following that URL)

The file cmtr_name_js.php is very simple, contain only one line:

var commenter_name = '<?=$_COOKIE['commenter_name'] ?>';

After making this change, my load went down considerably. I recommend this approach for anyone who has a high-traffic site that resides on a different domain (or sub-domain) than the MT installation domain.

This issue has been fixed in Movable Type 3.3!

Henrik, it has not been fixed in 3.3. I am using 3.33 and on Saturday my host killed my site until he could talk to me.

And now I can't remember all the places I need to change the name of the comment script, so I am sans-comments. However, unless this problem is solved by MT in a new update soon, I will be forced to switch platforms -- something I do not want to do.

Hi Henrik and Stephen - I'm not sure what issue it is to which you are referring. If it is the issue I am addressing with this article, all you need to do is bring your templates up to date as explained in the article. The problem is having old js and old template code with a new version of MT.

If the issue you are addressing is the one of the blog URL in a different location/domain from the CGI script, then I'm not sure what you can do other than Mark's PHP solution.

Oh my gosh... I can't believe I FINALLY found this post!!!! I was pulling my hair out with the system load issues related to MT.

I actually thought it was comment spammers killing my server. Why in the HELL is this fix not set up as a default????

Vic

@Vic -

Actually this is a default.

The problem with a default is that it's only good when you're creating a new blog.

Once you've done that, it's in place, and it's virtually impossible to catch all the customized templates that are out there, so from time to time an old one might slip through, which is why this was posted: To let people know how to fix the problem. Aren't you glad it's such an easy thing to fix?