Has anyone been able to discover how to add the Forbidden text rule to the form? I can't seem to find it in the list of validation rules.

Hello Robin.

Did you tried to add rule "existing in database" and create a special column in your database , where exactly the forbidden text is specified?

Regards:Vulcho.

I set up connection and database works fine, and does the validation, but this does not work for example on a form textarea. It only fires if the user types exactly what is in the database, it does not validate the entire string.

e.g.
a database column entry is 'First place'
'First place in search engine': does not fire an error
'First place': does fire an error

If it only works for exact match this would be impossible to setup.

In the Messages tab there is a rule, forbiddencond, with the message, 'The field contains words that are not allowed by the spamfilter'

How is this attached to the form?

There is a validation rule, Spam Protection, but where is the word list setup?

Thanks,
Robin

Hello Robin.

Quote

There is a validation rule, Spam Protection, but where is the word list setup?

After you apply the "Spam protection" rule you need to root in Scriptlibrary folder and open the "validator_forbidden.txt" which contains the words that are filtered.

Regards:Vulcho.

The problem with the Spam bot is I can not get past the error message. whether I fill in spam or not. It persists on the page and does not go away. Even with corrections.

Where do you set the form Action to post to another page. Currently the action changes to <%=DMX_validateAction%> which appends a '?' to the page.
On submit, the form is reset to blank and all errors are output on the page.

Hello Robin.

Can you provide me with link to the problem page?
Did you tried to apply the Spam protection rule without using bot check?


Regards:Vulcho.

This reply was removed on 2/8/2013 8:57:22 AM.
See the changelog

I found that the Spam Protection rule only works if you post back to the same page using the action <%=DMX_validateAction%>. So this does not allow for sending form results to another page as we have seen in several posts.

What is required here is to check for errors then forward if there are none.
If error = 0 then
'iterate form items to session variables.
'forward to another page.

Until this is addressed the Spam filter is useless.

The Bot check traps any input blank or otherwise and does not allow submission in any form. I don't see this function as useful.

The Ajax Exists in Database rule does work, but now you have to maintain a database for the rules and add a database connection.

Perhaps my finding can help others who are struggling with Spam validation.