Don't Back Down

Posted by Chad Everett on February 22, 2005

MT-Moderate 1.0.0 »

I've made some changes to MT-Moderate. The most significant change is that I've added the moderation of trackbacks to the plugin. A replacement for the Movable Type list_ping.tmpl is included to enhance this process, and the ping notifications have been updated as well.

If you have used a prior version of MT-Moderate - including the recent betas - make sure you remove the corresponding contents from other locations (primarily extlib/jayseae and extlib/jayseae/moderate). If you do not remove these files, your results will be, at best, unpredictable.

More detail can be found in the text file that is included in the archive. Please let me know if you have any problems, questions, suggestions, donations or revelations.

Announcement. Download.

Related Entries

Comments (13)

I've just installed this into my new MT3.15 installation and am running into a slight problem. I'm not sure if it is related to MT-Moderate or not, but it did appear after installing the files in this package.

On my main MT Admin page as well as after hitting "post" to submit a comment I get the following message: "Unrecognized escape \m passed through before HERE mark in regex m/C:\docs\cgi-bin\m << HERE t\plugins/ at c:\docs\cgi-bin\mt\lib/MT.pm line 307. Status: 200 Pragma: no-cache Content-Type: text/html; charset=iso-8859-1"

I do still have all the files from the older version of MT-Blacklist (v1.6.4) from before I upgraded to MT3.15, should I get that uninstalled before using this plugin? I know that version of the Blacklist won't work with my updated MT, so I should probably remove those files... Is this likely to be causing a conflict in the meantime?

Is this anything you have seen before?

-=kt=-

BTW, the moderation does seem to be working, in spite of that chunk of error code appearing.

Attempting to post a comment (in a post of any age) gets that error message, but the comment does appear in awaiting approval in my MT admin...

-=kt=-

Could we have a list of the previous files to delete - I don't have the 0.5zip any longer.

This message has to do with MT on Windows, not specifically this plugin. Though this plugin does use the method that causes this error, so they are sort of related. I'm going to put together something that may solve the problem.

If you are using any version prior to 1.0.0, just delete:

      plugins/Moderate.pl

If you are using one of the 1.0.0 betas, delete:

      extlib/jayseae/moderate.pm
      extlib/jayseae/moderate
      extlib/jayseae/moderate/comments.pm
      extlib/jayseae/moderate/trackbacks.pm

And that should do it.

Interesting, I am using a Windows server... The strange text never showed up until the Moderation plugin was installed, though. Will be looking forward to seeing what you can come up with to resolve this. In the meantime, I'll uninstall Moderate to see what happens...

Thanks for the info!

-=kt=-

KT, I sent you an updated version already. Please try it out and get back to me. Thanks!

Is using 0 valid for DIFF_ENTRY and DIFF_COMMENT. I am really do not understand what both variables are for, but I want to moderate ALL trackbacks, as most ALL is spam, no matter how old is it. I assume a value of 0 will force all trackbacks to be moderated?

Thanks!

Ken

A value of 0 is valid, however it will still allow any items through that come in the same day. You should be able to use a value of -1 to accomplish what you want. Please let me know if it does.

-1 indeed worked! I got a flood of TB spam today and it forced moderation on it all. Great plugin!

Looks like we have the Windows server issues ironed out. Please see the most recent entry for the most up-to-date information. Special thanks to Iain and Kate for their help on this.

I got e-mails when some spammer had trackbacked my MT blog. They all said the trackback had been moderated. So I put off cleaning the blog until after I'd blocked the spammer. Come to find out by accident, ALL the trackbacks were visible in the blog. Quite embarassing! Was that a one off on my blog, or typical?

But I like the way it works with auto-approving comments from commenters whose posts I'd approved before.

If you are using standard MT tags, they should not show. If you are using a plugin, such as SimpleComments, then they might - it depends on whether you have done anything to the plugin or not.

Leave a comment