No Captcha Error on Submit

When I leave the Captcha field blank, it gives me a warning that the code is wrong (not blank). But when I submit the form with a wrong code, I don't get any error at all. The form stays populated and does not submit, but to an end user, there is no way for them to know that the code was wrong.
I'm using version 1.0.6 of Visforms.

The error class on the div is set to display "none" in the CSS. I'm assuming that an error would change that display to "visible", but I don't see anywhere in the JS where that happens.

I don't care if it's the default message or the custom message, I just want the user to know that they have input the wrong code.

Thanks for any help you can give.

Michael Kadrie

Hi Michael,

can I have a link to the form?

I will take a look at it as soon as possible.

Regards,
Aicha

Not sure what happened. I thought I posted the link and now it's not here.
2500smallman.com/contact-us.html
Thanks for the quick reply.

Hi Michael,

thanks for the link.
Everything looks fine concerning visforms itself. I tried, just in case, and with the correct captcha I could submit the form. And I could reproduce the behavior you described with incorrect captchas.

The only thing I can think of at the moment is the following.
The validation about whether there is an input in the captcha field at all (not left empty) is done by Javascript on the client. (Which works).
But the captcha validation itself is done on the sever (php). This is always so when you work with captcha, it's how captchas are implemented. So the form is submitted even with an incorrect captcha but the submit is stopped immediately on the server. Visforms throws an error message and shows the form again with all inputs the user has made. The error message is added to the Joomla! message buffer and should be shown with the reloaded form. But it is the job of the template to get the message buffer content and show it. Maybe your template doesn't do the job? Please check your templates index.php. There should be some code like jdoc:include type="message".

Kind Regards,
Aicha

I suspected it might be that. I'll look into that and let you know if that fixed it.
Thanks again!