Everitz Consulting

At the top of the settings screen you have a field that allows you to set the name of the Static Beacon. This is a hidden field that is added to your comment form. The value of the field is checked when the form is submitted. If you want to change the name of the beacon, enter that name here. If you change the name, you'll need to rebuild your templates.

Whether you change the name of the beacon or not, you should decide what to do if the beacon isn't found on the comment submission. Since this is a static beacon - that is, it is generated by Movable Type and not by JavaScript - there should be no reason that this beacon isn't found. The only time it won't be on a comment is if the comment comes from an invalid submission - for instance, if some automated spammer submits a comment directly to your comment script, and that's a bad thing.

You can also choose to encrypt the value of the beacon. This simply adds another layer of complexity to your system, which makes it harder for an automated posting to happen by encrypting the beacon with a value that isn't likely to be known by a robot. It's not difficult to guess this value when not encrypted (as the value is stored elsewhere on the page), but by encrypting the value, it's nearly impossible, which adds an additional layer of protection.

Just below the name of the beacon you get to decide how to handle the situation if the beacon value is incorrect or missing entirely.

You can set the value to Off, this test is not applied to the comment.

If you choose Moderate, then the comment is sent to moderation rather than being published.

Neither of these values is suggested, however, because you should always have a beacon (see above).

You should either Discard comments (don't accept them at all) or Junk them.

If you choose to Junk comments, you can adjust the weight of the junk score, and you may want to assign a heavy weight to this condition, since it should never happen.

Return to configuring the MT-Approval plugin.