Hi,
I am having problems with sending emails as an event when I add Google No Captcha. I can not see any errors in Apache etc. Other actions work (like display, dbsave) but not the email. If I remove the GNC then all works (as in the email is received).
I have looked everywhere for an answer but can not find one.
Please can someone give me some advice as I am stumped!
Thanks,
HB
Hi hwbarton,
I don't see any obvious reason for this. Please drag a Debugger action into the On Submit event, then submit the form and post the debug - including the 'dummy emails' results here.
Note: if you are using the Easy Wizard you can turn on Debug on the Others tab in CFv4 or the Setup tab in CFv5.
Bob
Hi hwbarton,
I guess you took the email part out of the Debugger output??? It would help to see that too.
How do you have the Check NoCaptcha action set up?
Bob
Hi,
No not at all. What is in the post is all the output. I suspect that might be the problem.
The debugger is in and the email as well (see attached). As I say if I take out the recaptcha the email works.
Happy to send anything else to you to help solve this problem. I just can not get it.
BTW thanks for all your help. It is greatly appreciated.
HB
Hi hwbarton,
Hmmm . . . that looks OK, I'm not sure what is happening. By all means PM me the site URL, the form name, and a SuperAdmin login and I'll take a quick look.
Bob
Hi Bob,
OK so it was a conflict with caching issue. I have turned off all website caching and all works fine. Turn on caching and the email does not send. I can see lots of information on caching issues. I will review and implement a workable solution.
Thank you for all your help.
Howard
Hi HB,
The problem with caching forms is that the Captcha methods mostly rely on a unique key that is created when the form is loaded and saved in the User session for checking after submission. If the form is loaded from the Joomla! cache then the key will not match and so the check will always fail.
If caching is important then you can add a 'true' HoneyPot check to your form (not the ChronoForms one). This is a normal text input hidden with CSS so that a human user can't see and therefore won't complete it. A bot does see it and typically adds something. You then check after submission to see if any value is set, if it is, reject the submission.
Bob