Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.A Drupal 7 version would still be nice to support older Drupal Websites.
Should not be too hard, so if someone is interested to sponsor development, the maintainers could do that :)
Issue fork friendlycaptcha-3236280
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
anybodyComment #3
anybodyPostponed until someone sponsors the development.
Comment #4
john_b commentedI made a D7 version. Unless the maintainers say they prefer me not to, I will post a tar file here soon.
It is fairly straightforward apart from one gotcha: if you make the post request which sends the solution to Friendly Captcha using drupal_http_request() it will fail. The reason is probably that that function uses drupal_build_http_query(), which decodes slashes, and often there is a slash in the solution.
Comment #5
anybodyHi @John_B can't you please post a patch file or create an issue fork? Zipped repositories are dangerous as you can't know their contents. So indeed nobody should open it ;)
Comment #6
john_b commentedOK. Once I have tidied up the admin form, which I will get to in a week or so, I will do that.
Another gotcha for me was copying the API / secret key field on the admin form from the reCaptcha module, where it is limited to 40 characters--too short.
Comment #8
john_b commentedI have this working on PHP 7.3.
Comment #9
john_b commentedComment #10
john_b commentedComment #11
anybodyThanks, I created a Drupal 7 branch for you, so I guess the MR will need a rebase. Or close and create a new one, if that's too hard. We're at an early point yet.
Comment #12
john_b commentedYes rebase is too hard... I did a fresh commit to the new branch.
Comment #15
anybodyThank you very much @John_B, code is looking really good!
Sadly you selected the wrong merge target (1.x) in the MR. You have to select 7.x-1.x. Now it needs a rebase again... ;)
Comment #22
anybodyThanks @John_b. I also hate the currently missing piece of syncing the issue fork with the base repo... which leads to this trouble and rebasing... I just picked your code and created an alpha release, please have a look :)
Thank you sooo much for that great work!
Let's proceed with adjustments in a follow-up issue. I'll create one.
Comment #23
anybodyComment #24
anybodyUpdate: Code-style seems to be okay, tests don't complain... Of course some of the 1.x issues could also be implemented for 7.x-1.x but that's just improvement. THANK YOU SO MUCH! :)
Comment #28
john_b commentedSorry about the confusion with git.