• Anonymous
  • Login
  • Register
BlogSphere - Feature Request: Add additional spamblocker code


Hi guys,

I added some code to Bruce's blog that helps blocking comment spam.
In the first version (which worked nicely btw, but I'm a bit paranoid sometimes), I added:

1) Two fields to the $$viewtemplate for plinks, one value "" the other one computed text with the value of txtdocid
2) Same fields to the storycomment form
3) set field one to the value of field two in the comment.js just before the submit
4) compare the values in the wqscomment, if no match set doc.saveoptions = "0" print a message to the user and stop the agent

The reason I changed this lateron is that some of those automated posters fill all the fields they encounter, and if they happen to set the fields to the same value, the check would fail.

So I changed the first field to a div with computed text (txtDocID) and in the comment.js i read the value and replace the div.innerHTML with a HTML field set to the same value.
In the WQS i check the field value.

I think that is enough to discourage most spammers, and if not it's very easy to change the computed text value to a @today string or something.

If you find a better solution let me know.....





Taken Actions by Owners



Documents
In this field you can enter the actual request.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.
In this field owners can describe what they have done or want to do.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.