All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Please read about the changes to BoldMinded add-on licensing.

Ticket: Snaptcha prevents Freeform Next form submissions

Status Resolved
Add-on / Version Snaptcha 3.3.1
Severity
EE Version 7.4.11

John Faulds

Jun 30, 2024

Hi Brian,

I’ve just upgraded a site that was running EE 6 to 7.4.11 and in the process upgraded Freeform to 3.0.5 and Snaptcha to 3.3.1. All forms were submitting successfully prior to the upgrade, but after the upgrade, Snaptcha was flagging everything as spam with the error in logs being that the snaptcha field wasn’t found although I can see it in the code (screenshot attached).

After disabling snaptcha, forms submitted OK. Also, I’m not sure the site actually needs snaptcha anymore as Freeform has a built-in honeypot solution now too.

Cheers John

#1

BoldMinded (Brian)

Did you see this thread? https://boldminded.com/support/ticket/2915

#2

John Faulds

Well, that’s very strange. Changing the form parameter to form_name on the exp:freeform_next:form tag enables the form to be submitted successfully with Snaptcha running. But form_name isn’t documented and it’s not in the demo templates that Freeform installs with. :?

I’d actually already submitted a ticket with Freeform about it over the w/e before I thought about Snaptcha maybe being involved, so I’ll follow up with them when they get back to me.

#3

BoldMinded (Brian)

Yeah I don’t know what has changed on Freeform’s side, but something has. If it was a mistake on their side and something in Snaptcha needs to change, then it sounds like the Freeform hooks just need to be disabled so that Freeform handles spam on it’s own.

#4

Niki Wolf

Actually I heard back from Solspace on that, as I’d opened a support case with them as well.

Freeform 3 (aka Freeform Next, or the new Freeform) uses and recommends "form" as the parameter, however, it does have an alias for "form_name", as that is what it used to be in Freeform "Classic". Freeform "Next" made large improvements to spam protection that basically did a lot of the same things Snaptcha did, so there wasn't much need for Snaptcha with Freeform anymore. That said, Snaptcha may have changed since then and perhaps has some advantages over Freeform's built-in options.

My hunch here is that maybe Snaptcha is looking for the old "form_name" parameter (which was valid for old Freeform Classic) and NOT the newer "form" parameter, and it might be a change required on their end. I can't think of any reason why Freeform itself would care about which parameter was used. :blush:
#5

BoldMinded (Brian)

Snaptcha doesn’t care what the Freeform tag names are… it doesn’t look at or expect “form” or “form_name”.

#6

BoldMinded (Brian)

I’m going to add an option to disable Freeform support in the next version of Snaptcha since it sounds like they’ve added there own spam prevention.

Login to reply