Waitlist by Tess using reCaptcha v3

[lesliekirk]

The Waitlist by Tess has a place to reCaptcha v2 (which I never really figured out). can the reCaptcha v3 module be used with it? If so, how? I'm thinking assigning it to the PROD might cause some issues.

[SteveG]

Reviews by Tess also has reCapptcha v2 which lets too many spam reviews through, be good if recapture v3 would work for it too?

[Nick]

Currently the reCaptcha V3 module does not work with modules outside of the native software. Our software team is in the process of building in support for modules to use the built in reCaptcha V3 functionality.

That being said the Waitlist by Tess module does have a Pre-Logic Template feature (see page 20 in the documentation) that you could manually add the reCaptcha V3 JavaScript to so that the module will support the feature without using the Miva built in functionality.

[lesliekirk]

That being said the Waitlist by Tess module does have a Pre-Logic Template feature (see page 20 in the documentation) that you could manually add the reCaptcha V3 JavaScript to so that the module will support the feature without using the Miva built in functionality.

Have I mentioned how difficult it seems to be for the average Jane to follow along with the documentation for Waitlist by Tess module? Now if you want to see some excellent documentation, the GA4 configuration docs are OUTSTANDING. Whoever wrote those needs to be the technical writer for all the docs (IMHO).

[lesliekirk]

Currently the reCaptcha V3 module does not work with modules outside of the native software. Our software team is in the process of building in support for modules to use the built in reCaptcha V3 functionality.

That being said the Waitlist by Tess module does have a Pre-Logic Template feature (see page 20 in the documentation) that you could manually add the reCaptcha V3 JavaScript to so that the module will support the feature without using the Miva built in functionality.

Well, that could explain a LOT of the problems I've been having. FWIW, I wasn't the one who did the install/configuration of reCAPTCHA v3. Makes me wonder if the Reviews module cannot use v3 either...

[lesliekirk]

Currently the reCaptcha V3 module does not work with modules outside of the native software. Our software team is in the process of building in support for modules to use the built in reCaptcha V3 functionality.

That being said the Waitlist by Tess module does have a Pre-Logic Template feature (see page 20 in the documentation) that you could manually add the reCaptcha V3 JavaScript to so that the module will support the feature without using the Miva built in functionality.

Any update on this?

Question - the store I am working with has a pop-up form to submit the email. An WAITLISTADD Action was created in the reCAPTCHA v3 Action Configurations but it's not active. It created the following error at the BASK screen:

The requested action cannot be performed at this time.

Is there an example of this for v3?

<mvt:comment>
| | reCAPTCHA check (v2) |
</mvt:comment>

<mvt:assign name="g.secret" value="'MY SECRET KEY'" />
<mvt:assign name="g.response" value="miva_variable_value( 'g.g-recaptcha-response' )" />
<mvt:assign name="g.remoteip" value="s.remote_addr" />
<mvt:assign name="l.google_response" value="''" />

<mvt:call action="'https://www.google.com/recaptcha/api/siteverify'" method="'POST'" fields="'secret,response,remoteip'">
<mvt:assign name="l.google_response" value="l.google_response $ s.callvalue" />
</mvt:call>

<mvt:if expr="NOT miva_json_decode( l.google_response, l.data ) OR NOT l.data:success">
<mvt:assign name="g.Waitlist_PreLogic_Continue" value="0" />
<mvt:assign name="g.Error_Message" value="'Invalid reCAPTCHA'" />
</mvt:if>

TIA - Leslie

[Nick]

lesliekirk the native reCAPTCHA V3 module will work with Waitlist by Tess module if setup correctly. The waitlist <form> needs to be rendered on the page and NOT created by JavaScript.

For example, some "pop-up" integrations will use JavaScript to copy a div or render an iframe in a newly created styled "pop-up" window. Because the form that reCAPTCHA needs to read is not rendered on the page it will not work. If this is the case then my suggestion would be to update the "pop-up" functionality to something similar to the way the native Shadows framework uses. Shadows renders the "pop-up" content on the page then using JavaScript and CSS to complete the "pop-up" functionality. This method will work with the native reCAPTCHA v3 module.

[lesliekirk]

lesliekirk the native reCAPTCHA V3 module will work with Waitlist by Tess module if setup correctly. The waitlist <form> needs to be rendered on the page and NOT created by JavaScript.

For example, some "pop-up" integrations will use JavaScript to copy a div or render an iframe in a newly created styled "pop-up" window. Because the form that reCAPTCHA needs to read is not rendered on the page it will not work. If this is the case then my suggestion would be to update the "pop-up" functionality to something similar to the way the native Shadows framework uses. Shadows renders the "pop-up" content on the page then using JavaScript and CSS to complete the "pop-up" functionality. This method will work with the native reCAPTCHA v3 module.

Thanks, Nick, but what if the store owner does not want it rendered on the page?

[Nick]

lesliekirk then you would need the Pre-Logic Template feature (see page 20 in the documentation) and manually add the reCaptcha V3 JavaScript to so that the module will support the feature without using the Miva built in functionality. I don't have an example of this as it not common practice, rendering the form on the page is the recommended way to implement.

[lesliekirk]

FYI - the Raw Source links in the documentation are broken.