-
Notifications
You must be signed in to change notification settings - Fork 61
"Invisible" reCaptcha no longer works (prototype 1.7.0) #56
Comments
Yes, Iam getting very same error message. I can not figure out so far what is going on. |
Same thing:
Also it is impossible to login from admin backend: |
In the short term you can disable the module in |
Hello, I will ave a look into this soon, thanks for reporting. |
Did any of you update the module recently? can you check versions installed please. latest is 2.5.0 |
Is this all admin/backend related? I am not seeing issue on frontend with latest
|
I tested it on the following versions and unfortunately it doesn't work: 2.1.1, 2.5.0 |
Magento version? |
I'm on the latest currently, per config.xml - 2.5.0 I'm seeing the same web console error on both backend and frontend, when trying to use "Invisible" CAPTCHA type. |
Magetno 1.9.4.2
2021. 06. 21. 18:15 keltezéssel, Lucas van Staden írta:
…
@indrisepos <https://github.com/indrisepos>
Magento version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTRWGVRTIZ5NHQ2JIBL673TT5QSRANCNFSM47BMDHDQ>.
|
anyone have a site that I can have a look at? obviously a test / uat site is prefered. I cannot reproduce. |
I am on latest openmage, so will get a standard Magetno 1.9.4.2 setup to see. |
I have 2.0.1 and its not working. |
I can confirm that the same bug exists in 2.3.10, 2.4.0, 2.4.1 and 2.5.0. The same error is produced in the web console when using "Invisible" reCaptcha type. I get the error - and failure of reCaptcha - on backend and frontend. The fact that it spontaneously stopped working on or around 17/06 makes me think the problem is external.. something relied upon that is no longer the case? Parameter(s) changed, etc? @ProxiBlue do those versions you are testing have a newer Prototype version? I am on 1.7 according to |
Ok I've made progress... Replacing I don't know what if any compatibility issues there are with Magento 1.9+ using Prototype 1.7.3 instead of 1.7.... EDIT: OpenMage ships with 1.7.3 so I'm inclined to think it might be ok. Not sure how you'd debug this one @ProxiBlue - it seems the problem is localised to Prototype which is outside the scope of your module. |
gives https://www.google.com//recaptcha/api/verify which gives 404. |
I have seen this before, let me check my changelog |
The 404 is expected: It requires POST data |
no, I was wrong, a few commenst down: |
it should be siteverify not verify |
Yeah I was wrong too - it's https://www.google.com/recaptcha/api/siteverify I don't see the old URL with just "verify" in the source..
|
ok, is 1am here now, I need to go get some sleep. I will investigate on a clean m1924 when I wake up again. It is installed already, will check module in that next. Sofar all my local tests work fine, no issues |
👍 Upgrading I suspect if all your local tests are fine you're using OpenMage, which ships with Prototype 1.7.3. Magento 1.9.4.5 and below ships with 1.7. |
Ok, so is likely why mine works on openmage, as they upgraded that. Thanks for that, I will have to check the code and make it backwards compatible, OR, is code on google side with their js that's no longer compatible (which seems likely reason) |
I can confirm that the fix by @empiricompany fixes the issue. (Thank you very much for that effort, I have been stick on a paid client job) It is really the only way as the issue is outside this modules functionality/scope. I will update the readme accordingly, as this fix introduces a new version of prototype, which can potentially cause (but unlikely) issues with other parts of the magento framework |
It appears to fix the frontend, but the backend is still pulling |
I will have a look at that, thanks for letting me know, did not check admin. |
Check new version 1.5.2 |
yes we have fixed only frontend because we not use captcha in admin, but if we want to cover also admin i think we can simply just register the observer into section in config.xml
|
Yep, I have adjusted the the event to the global section |
No joy for me, I'm still getting the standard Magento |
Not in my local. let me check the release, see if it released correct code |
You are correct. I tested that on the 1.7.3 based magento (as my debugger is not working on the docker environment I quickly brought up for the 1.9.4.5 test) Although the code actions the end result is still the wrong (core) prototype loading in head, so admin is somewhere replacing that again with the default) Fixing my debugger so I can dig into this |
does not help I am now so used to m2, I forget how parts of m1 works! |
it's hardcoded in adminhtml/default/default/template/login.phtml |
Oh FFS, yes I just found it as well |
Well spotted. |
At this point I think a patch will need to suffice to make that template work on the module supplied 1.7.1 Its just one of those things. |
I have work waiting that I need to get to |
Indeed. To be honest given how many places this might be the case, it might even be worth just telling people they need to stick It's hardcoded in |
i think there is not a clean solution to fix it in backend login, you have to manually update original js/prototype.js or we have to rewrite entire login.phtml template |
So, the fix will be to move the provided fix back to just on a frontend event, and supply a patch for login.phtml that can be applied |
if composer is used for site deploy via a composer patch, it can be applied cleanly-ish via pipeline deploys and composer udpates I will supply instructions in README |
...are the affected files for the backend, for what it's worth. I wonder if there is any mileage in trying to patch the incompatible functionality in |
Ok, I have reverted the event back to frontend only on version https://github.com/ProxiBlue/reCaptcha/releases/tag/2.5.3 I need to move on to paid work, with deadlines. I have updated readme. When I get time (unless someone beats me to it) patches will be supplied via a GIST to apply these changes manuall, or via composer patches |
if you are stuck with admin login you can disable captcha with:
for admin, then clear cache |
ATTENTION: I am currently considering archiving this module, as I no longer have the free time to continue supporting this code. I simply don;t have teh time due to paid works with deadlines to work on this at present. |
Hi,
I am running Magento CE 1.9.4.5 and as of about 17/06/2021 the "invisible" reCaptcha no longer works on my website. It does not appear in the bottom right (as configured), and attempting to log in to the backend with a known good username/password combination just results in an error, as if the reCaptcha part is missing.
When the reCaptcha is set to "Invisible", I get the following error in my browser web console:
Changing the reCaptcha to "I am not a robot" eliminates the above error, and the user can log in - with the visual "I am not a robot" click required.
I have experienced the same behaviour on a development Magento website which has not been changed in over a year, so I'm convinced that something is no longer playing nicely together.
Anyone else experienced this?
The text was updated successfully, but these errors were encountered: