ricgetli
I would urge people converting from MT comments to take some additional steps to stop MT comment SPAM which can still happen even when it's not displayed.
You should use the HaloScan code snippet to replace
<MTEntryIfAllowComments> </MTEntryIfAllowComments>tags and everything in between them. If you do not replace the tags, the spambots can still spam your MT commenting system--it just won't be displayed, but it will slowly eat up your webspace.
You should put the two HaloScan snippets into the appropriate areas of both the HEAD and BODY of all the templates you use: Main Index, Date-Based Archive, Category Archive, and Individual Entry.
There should be no reference MT Comments in these templates when you're finished.
Now, the fail-safe: After you've ported in your comments, you can simply remove mt-comments.cgi from your cgi-bin, (I'd make a back-up copy, just in case). There is now no MT Comment machinery for the spammers to attack.
If that last step seems too drastic:
Go here∞
Download mt-close.zip and open mt-close.cgi.
Do a Find and Replace to change the number "5" in the script to "1". This closes the ability of spammers to leave any MT comments for past posts.
Then, go to Weblog Configuation, and on the Preferences tab, turn Allow Comments Default to NONE. This fixes it for new posts.
Original information provided by frimmin∞
Minimise Comment Spam on Older Posts
The following information is for Movable Type users only.I would urge people converting from MT comments to take some additional steps to stop MT comment SPAM which can still happen even when it's not displayed.
You should use the HaloScan code snippet to replace
<MTEntryIfAllowComments> </MTEntryIfAllowComments>tags and everything in between them. If you do not replace the tags, the spambots can still spam your MT commenting system--it just won't be displayed, but it will slowly eat up your webspace.
You should put the two HaloScan snippets into the appropriate areas of both the HEAD and BODY of all the templates you use: Main Index, Date-Based Archive, Category Archive, and Individual Entry.
There should be no reference MT Comments in these templates when you're finished.
Now, the fail-safe: After you've ported in your comments, you can simply remove mt-comments.cgi from your cgi-bin, (I'd make a back-up copy, just in case). There is now no MT Comment machinery for the spammers to attack.
If that last step seems too drastic:
Go here∞
Download mt-close.zip and open mt-close.cgi.
Do a Find and Replace to change the number "5" in the script to "1". This closes the ability of spammers to leave any MT comments for past posts.
Then, go to Weblog Configuation, and on the Preferences tab, turn Allow Comments Default to NONE. This fixes it for new posts.
Original information provided by frimmin∞