-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated reCaptcha integration to use the 2.0 API. #21
base: develop
Are you sure you want to change the base?
Conversation
8c8ab80
to
36ab354
Compare
Thanks! Am I right in assuming that ReCaptcha v2 will be displayed but there are some final steps missing? After all, I constantly get the message that the recaptcha was not filled in correctly after clicking the post button. |
This should just work out-of-the-box - I've tried it on a fresh install of MODx and it seems to be fine. It may be worth checking that you're using a v2 compatible key. What's the exact error you're seeing? |
I created a new ReCaptcha key to ensure that it is v2 comaptible but the error still exists. The exact error is: "The reCAPTCHA wasn't entered correctly. Go back and try it again." (lexicon-key: recaptcha.incorrect). Additionally, I have checked all file changes line by line. The files in core/components should be identical. |
Scanning through for that error, it looks like that will get invoked if you're using comment previews. I hadn't spotted that was also using reCaptcha, and I've updated the logic there to match |
Unfortunately nothing changes. The QuipReply looks like this:
Some notes:
|
Hmm, I'm still not able to replicate this one. The issue with The only other debugging step I can see is to actually take a look at what response you're getting back from reCaptcha - could you get the values of |
The
The |
Okay, that's interesting - the fact that it's returning the
does this make any difference? If not, it would be useful to know what value |
No changes so far: The |
That...sounds wrong.
I can't see any set of circumstances that would obviously cause |
In order to guard against misunderstandings:
and
It seems that |
It seems that the error is in this code snippet:
|
Hi - does this actually work? |
No description provided.