WebisComm

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)

WebisComm
Participant

Hello,

thank you for your previous reply — the 401 error issue was successfully resolved by adjusting our REST API configuration.

However, we have now identified a different problem: the reCAPTCHA validation on the “Email to Download” form does not appear to work correctly.

The reCAPTCHA field is displayed on the front-end, but when a guest submits the form, the request payload does not include any g-recaptcha-response parameter, and the email is sent successfully even if the captcha checkbox is not checked.

In other words, the front-end widget is loaded, but the token is never attached to the AJAX request, and therefore no real validation occurs on the server side.

We are using reCAPTCHA v2 (“I’m not a robot” checkbox), and the keys are valid (already tested).

Could you please check whether the current WPDM version (6.8.3) properly sends and validates the reCAPTCHA token on the /wp-json/wpdm/email-to-download endpoint?

This seems to be a regression, as everything else now works correctly after the REST fix.

Thank you in advance for your help,

Regards.


WebisComm
Participant
This reply has been marked as private.

WebisComm
Participant
This reply has been marked as private.

WebisComm
Participant
This reply has been marked as private.

WebisComm
Participant

Hello,

I’m currently using **WP Download Manager Pro 6.8.3** on a live production site and I’m still facing a critical issue with the **Email Lock form** when reCAPTCHA v2 is enabled.

The reCAPTCHA widget appears correctly on the frontend, and the “Protected by reCAPTCHA” badge is visible, but when users submit their email, the process fails silently and no download email is sent.
In the browser console, I consistently get:

POST /wp-json/wpdm/validate-captcha → 401 (Unauthorized)
POST /wp-json/wpdm/email-to-download → 401 (Unauthorized)

The site and secret keys are correct, server-to-server validation with Google works (tested manually), and the SMTP configuration is verified and functional.
This behavior clearly indicates that the reCAPTCHA token is not being passed correctly to your REST endpoint — a known issue already mentioned by several users since version 6.8.2.

Please provide the **latest WPDM Pro build (6.8.4 or higher)** that includes the fix listed in your changelog:

> Fixed: reCAPTCHA validation issue causing 401 Unauthorized in Email Lock form on some setups.

This is urgent — we rely on WPDM for secure file delivery and the feature is currently broken on all my production domains.

Best regards.

Viewing 5 posts - 1 through 5 (of 5 total)