Community Support Forums

The reCaptch on my registration is not working. Initially, it was simply giving a warning that the code was being entered incorrectly but now I am getting the following warning where the reCaptcha should be: 'An internal error occurred: 4B1DED7FA5570.A897313.431'

I have removed the captcha="clean" from the Pro Forms code but set up a temporary page (Trial Temp) so you can view the error: http://b4thestreet.com/main/trial-temp/

Any help is greatly appreciated. Thanks in advance.

Try changing the value to red, and make sure that you haven't declared clean more than once.

If neither of those things work, can you try to redo the Pro Forms again?

Thanks for the quick reply. What do you mean by; "Try changing the value to red.."

I think he means that instead of:

Code: Select all

captcha="clean"

you put it like this:

Code: Select all

captcha="red"

I tested with captcha="red" and am still getting the same security warning: 'An internal error occurred: 4B1DED7FA5570.A897313.431'. Thanks for the suggestion though.

I'm having this exact same problem. Solution offered above does not work for me either. No problems with this form yesterday, and have not altered the form since then (except to try the solution above).

'An internal error occurred: 4B1EF74EEE138.A88CD08.73EC'

This script is from Google. I'm having other Google issues this morning with Gmail unable to deliver email to email addresses I know are good. Maybe this issue is a Google problem?

If I delete captcha="clean" from the shortcode, captcha is eliminated, and the form works: OK while we're in beta testing. Hopefully, this really is a rare Google glitch, and it will work again soon.

I'm getting this one today too:

An internal error occurred: 4B1F0C622FDE0.A0CEF10.625

Thanks for jumping on this, Jason.

This error comes from the reCAPTCHA service. I've just done some research on this error. It appears to be a common issue among reCAPTCHA users. I've seen several reports about this in their support forums here: https://groups.google.com/forum/#!searc ... al$20error

After digging on this a bit, it looks like reCAPTCHA has suffered some data loss, which is what has caused this issue for s2Member Pro clients. The global reCAPTCHA public/private keys that the s2Member Pro application is distributed with, no longer exists, for whatever reason. Resulting in the error code.

In the short term, you can resolve this by acquiring your own public/private keys for reCAPTCHA ( it's free ). Please follow the instructions below. In the next release of s2Member Pro, we'll update the default global public/private keys and also make this a configurable option to avoid any further downtime associated with this in the future.

Please create this directory and file:
/wp-content/mu-plugins/s2-recaptchya-keys.php
( these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins )

Please acquire your own public/private keys with the link provided in the code below. Again, this will be addressed in a more formal way in the next release of s2Member Pro. This hack is just a temporary fix.

Code: Select all

<?php
add_action ("ws_plugin__s2member_after_loaded", "my_s2_recaptcha_keys"); function my_s2_recaptcha_keys ()
    {
        /* Get your own public/private keys, please go here:
            <https://www.google.com/recaptcha/admin/create>. */
        $GLOBALS["WS_PLUGIN__"]["s2member"]["c"]["recaptcha"]["public_key"] = "xxxxxxxxxxxxx";
        $GLOBALS["WS_PLUGIN__"]["s2member"]["c"]["recaptcha"]["private_key"] = "xxxxxxxxxx";
    }
?>

Thanks for resolving this issue so quickly!! Greatly appreciated.

I followed your instructions exactly and it worked 100%!! You guys rock. Thanks again

This fix is creating another problem associated with a different plugin:

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/nmtc/public_html/wp-content/mu-plugins/s2-recaptchya-keys.php:1) in /home/nmtc/public_html/wp-content/plugins/facebook-feed-grabber/facebook.php on line 127

Here's the code in the facebook feed grabber that is in conflict, in case that gives you more clues about how to avoid the conflict:

// The Facebook PHP SDK uses sessions. So start sessions now before anything is output.
if ( !session_id() )
session_start();

Try downloading the PHP file attachment instead. Header errors are usually attributed to extra white-space before or after the <?php ?> tags. This may have happened when you copied/pasted from the forum. The original file is attached though, please give that a shot.

Yup. A space before the opening <?php tag. Removing it fixed the issue. Thanks a bunch!

Thanks, people. I applied the fix and I'm back in business too. Thought you'd want to know!

Thanks for the great feedback, guys. Very appreciated, it really helps.

You guys impressed me with your quick support. Yet another reason to recommend s2Member to other developers.

It is probably me - but I have carried out the instructions - captcha is working again but the code when entered is never accepted, preventing all registration.
What have I missed?

virtuallight wrote:It is probably me - but I have carried out the instructions - captcha is working again but the code when entered is never accepted, preventing all registration.
What have I missed?

I would double-check your private key in this case. It sounds like your public key is correct, but your private is not, or has an extra space in it; something like that.

Great - thank you Jason - when I pasted the privet key in, it missed off the last letter!

I'm still having some issues mainly b/c I am not sure how to make a new directory... I tried opening Dreamweaver, connecting to my FTP and adding the folders, but its giving me an error message. Is there a plugin I can download instead that will do this for me?

Hi Guys

I've tried the fix mentioned above and I'm afraid I still have the internal error message. I followed the instructions and even used the file you supply, the plugin is recognised in wordpress as a must have but other than that, nothing! It's pretty bad now as our site hasn't been able to take any registrations for the past week.

Is there any word on when the update will be coming along that fixes this properly?