Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Snaptcha with AJAX
| Status | Resolved |
| Add-on / Version | Snaptcha 3.2.2 |
| Severity | |
| EE Version | 6.3.5 |
John Faulds
Mar 23, 2023Hi Brian, you say in the docs “If your forms use AJAX to submit data then you must ensure that the Snaptcha field and its corresponding value is submitted as well”. If I have a bunch of channel forms for bulk editing entries on the front end, how do I do that?
If I add {exp:snaptcha:field security_level="1" id="{entry_id"} to my template, it seems because it’s a supported add-on that gets ignored and Snaptcha automatically adds its own field.
Ideally, I’d like to be able to disable Snaptcha for these forms altogether as you can only access the page/s after logging into the CP anyway. But that doesn’t appear to be an option.
At the moment, I have to turn the security level down to low to submit the forms.
BoldMinded (Brian)
Hi, John. I’m a little confused, so you need snaptcha on some forms but not others?
As for the Ajax part, you’ll have to use JS to grab the captcha value and send it along with the post data.
John Faulds
> Hi, John. I’m a little confused, so you need snaptcha on some forms but not others?
Yes. The forms that are being tripped up are channel forms that aren’t available to the public anyway. It’d be good if there was a way to not have it enabled for certain forms.
BoldMinded (Brian)
Thats not how Snaptcha is built, it’s an all or nothing extension. The only way to disable it on some forms is to edit the exp_extensions table and find the hook that applies to the type of form in question, and then disable that hook call.
John Faulds
Thanks, editing the exp_extensions table suits my purposes.