5.x-2.1 captchas are silently ignored

Oh, whoops.... It's because this new reCAPTCHA version targets Captcha RC2, which hasn't been released yet. I'll talk to the Captcha guys and see if they can get a release out either tomorrow or the day after.

If you get Captcha 5.x-3.x-dev, it should work.... Sorry about that one!

Thought I'd make a 2.2 reCAPTCHA release because I found a couple of other bugs when testing with captcha 5.x-3.x-dev. Thanks for the notes! Let me know if you still have problems with using this with captcha 5.x-3.x-dev.

Same problem with 2.2 -- a blank response seems to go right through.

W

Hmm, does this only happen when you upgrade it? I'll do some case testing today.

I haven't had time to look carefully at this, but I notice that you removed the '#required' => TRUE from the captcha challenge form element. Adding it back in would seem like a quick fix.

Hopefully that helps. I should've kept that #required flag in there, don't know why I got rid of it.

this problem is present in the latest 4.7 dev release (Aug 22) too

jt

Can't reproduce on 4.7. On my setup, which is the dev version, leaving the recaptcha field blank correctly returns a fail. I need more info about your exact setup.

here's the list:

captcha-4.7.x-1.2
recaptcha-php-1.9
recaptcha-4.7.x-1.x-dev

PHP Version 4.3.9
MySQL - 4.1.20
drupal - drupal-4.7.7

guess i should check that is the latest version of captcha ...

jt

OK, it looks as if the api for recaptchalib.php has changed somewhat, and that may be the root cause.

I'm using recaptcha-php-1.8.

For the moment, I suggest you revert to that. I'll look at getting the module to work with 1.9 asap.

Testing with 1.9, I still can't reproduce your error. (The changes to recaptchalib.php make some of the code in the drupal module unnecessary, but don't seem to make a difference as far as operation.)

Can you try reproducing the problem after clearing your browser's cache?

I can't reproduce it either... Does the #required help the situation?

with an install of the dev version of captcha [4.7.x-1.x-dev | 2007-May-19 | 13.47 KB] this problem seems to be resolved. i didn't go back to the 1.8 version of recaptcha-php

thanks for your help!

/jt

I've committed a number of additional features since the version you reported problems with. Can you (or someone else) try to replicate the problem on the latest 4.7 dev? I've tested on both Firefox and IE and still can't repeat. If no one can reproduce the problem in the next few days, I'm going to close the bug and create a new stable version for 4.7.

ok -- i've tested the latest -dev version in my testing environment, and see themes (optionally), and a separate module to enable for mailhide.

both seem to be working correctly. i wasn't able to bypass the recaptcha in either place, using mac[safari/firefox] or windows[ie/firefox].

thanks!

/jt

This problem should be fixed with the 5.x-2.3 release. Anyone else have problems?

Yes- I'm using the brand-new 5.x-2.3 and it's still accepting empty responses.

W

BTW-- I'm using firefox (linux) 2.0.0.6 and same problem with Mac OS X firefox 2.0.0.6. Drupal 5.2. I'm up to date on all modules (captcha 5.x-3.0-rc1). I attempted to post a comment as an anonymous user. The Recaptcha block is there, but it accepts no input and doesn't make a peep.

Safari too. (Just checked) I do not have "skip captcha challenges" checked for anonymous users, so they should not be able to post a comment otherwise.

Am I doing something wrong?

W

You'll need Captcha 5.x-3.x-dev release to get reCAPTCHA version 2.3 to work. This is because there were some nice API changes that broke compatibility between Captcha RC1 and RC2. Captcha 3.0 RC2 should come within the week.

RC2 is out: http://drupal.org/node/171468

Setting version back to 5.x, since I've heard no further reports of problems with 4.7

Since the captcha API keeps changing, and since a silent failure is obviously a significant problem, what do you think about testing for the right version of captcha at least on installation, and warning the user if a version with an incompatible API is used?

"Backwards compatibility" was discussed, but we decided against it because the API was still in development. At Captcha 3.0 final, we'll keep backwards compatibility a priority.

Thanks for the help on this one, guys. Setting it to fixed as Captcha 3.0 final should be here soon, and the Captcha API is now pretty solid and won't change (much).