Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mollom logging support #3

Open
sminnee opened this issue Mar 31, 2012 · 0 comments
Open

Mollom logging support #3

sminnee opened this issue Mar 31, 2012 · 0 comments

Comments

@sminnee
Copy link
Member

sminnee commented Mar 31, 2012

From http://open.silverstripe.org/ticket/4551

Right now it is hard to do detective work with Mollom. Sometimes you might encounter a bunch of spam and it is not clear how this got through. Implement logging, such that;

When a comment is submitted, the piece of information is stored about how it was allowed to enter the website. For instance, the value might be:
a) Mollom CAPTCHA was presented and entered correctly b) Mollom beyesian filter detected this as being ham, and no CAPTCHA was shown c) No antispam system shown; comment let through without checking d) Comment was held for moderation and approved manually

Where extra information can be stored, such as a "score" of how spammy the content is, also keep this. I am not sure whether the Mollom API will provide this to us.

This information should be stored in the database and available to see when you use the CMS and open the pop up to view a comment.

Secondly, if it doesn't already, also store the IP address of the commenter, and make this easily accessible to investigate.

This information will allow us to recieve spam and have information on how to reduce it in the future -- for instance, we can create logic within SilverStripe?, or pass informed feedback to the authors of Mollom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant