WP-Prowl 0.7.2 released. Fixes reCAPTCHA issues.

Version 0.7.2 of WP-Prowl was just pushed to WordPress SVN, and should appear on the plugin page within the hour. This version should finally put the WP-reCAPTCHA plugin issues to rest. Previously, comments were being denied by reCAPTCHA, but were still being pushed out to Prowl as though they were proper comments.

reCAPTCHA’s implementation is strange, in my opinion. It still stores the comment in the database, which I assume is so that Akismet and others can still benefit from it being posted. Or perhaps (and more sensibly), so that it can deny duplicate comments should a subsequent comment pass reCAPTCHA? I don’t know the reasoning, but luckily, reCAPTCHA sets a global variable when a comment fails the CAPTCHA. Observe this simple fix:

global $recaptcha_saved_error;
if($recaptcha_saved_error) return;

Sorry if this fix is boneheaded in any way, but in all my testing it seems to work fine. This went into my comment handling function, and simply returns if reCAPTCHA set an error. I checked out the recaptchalib, and it seems to only set this global error variable whenever the comments fails to pass, so I’m going to call it good. Hopefully this helps out anyone having an issue. Let me know if not please!