Repository navigation
Conversation
…logging Reset the captcha after AJAX submissions, public JS events, log failed verifications (1.24.0)
…lookup with several forms
- User Registration's AJAX login posts only its own fields, so the
wp_authenticate_user check never saw procaptcha-response and rejected
every login. A jQuery prefilter now adds the token from the login form,
and a failed login resets the widget.
- Spectra reads hidden fields via getElementById('hidden'), which returns
the first match on the page, so a second Spectra form (or one with its
own hidden field first) sent the wrong or no token. Our input no longer
has that id; a hidden element whose id is the field name lets Spectra's
per-form loop send the form's own value.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sending `ip` to /siteverify turns on IP matching, which rejects real visitors when the IP differs from the one that solved the captcha. Most sites are behind Cloudflare, where REMOTE_ADDR is Cloudflare's address, so 1.23.0's default could reject legitimate submissions. - New "Visitor IP matching" select on the General tab, off by default: Cloudflare (CF-Connecting-IP), another proxy (first X-Forwarded-For address) or a direct connection (REMOTE_ADDR). - The prosopo/procaptcha/visitor_ip filter now receives the IP from that setting (empty when off) plus REMOTE_ADDR, and can still override it. - Unit tests for each source, the default and the filter. - Translations for the new strings in de, es, fr, it and pt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The widget calls error-callback for failed background requests too (e.g. the detector bundle or frictionless calls to the provider), which don't invalidate a token the visitor already has. Clearing our custom input on those emptied valid tokens in JS-driven forms; CI hit this with Formidable whenever the provider was unreachable. Expiry and reset still clear it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…and-spectra Turn off IP matching by default (setting), fix User Registration AJAX login and Spectra with several forms
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases 1.24.0 (#67, #68).
prosopo-procaptcha:filled,:clearedand:reset.verification_resultaction.The e2e "wrong value" tests are currently failing on every branch, including 1.23.0's own code.
/siteverifytimes out from the GitHub runners: the CI debug.log showscURL error 28after 20s. Merged on request, so the IP-matching fix ships quickly.🤖 Generated with Claude Code