maybe that update will solve the problem...
if not, we encountered a similar situation which we solved by taking out any carriage returns in the message. This simple issue was ruining all our cfinput validations on a form. Seems unlikely, but it was the source of our problem.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.