Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 reCAPTCHA not showing? | Event Espresso - Staging Server
We got some spam registrations, so we decided to implement reCAPTCHA. I created the public and private keys, saved them in my EE General Settings, and then tested a registration, but I don’t see the CAPTCHA request at all. Is there something else I need to do to make these appear? Is it just supposed to show up at the bottom of the registration page?
I read in older forum posts that a CSS rule was hiding them, but I don’t see anything in the HTML source, either (but I guess if it’s using an iframe, I might not). What would I look for in the CSS if that was the problem?
Yes. I created the keys using just the domain name compassclasses.com because that’s what the instructions said. I wonder if I need to set up the keys for http://www.compassclasses.com instead? But I don’t think the problem is for lack of an API key… I would think EE would throw an error if that was the issue. I am just seeing nothing at all.
Are you logged into the site when you check the registration page for reCaptcha? The reCaptcha fields will only appear for logged-out visitors of the site.
Oh! Yes, that was it. I had a feeling I was missing something obvious. Thanks!
Viewing 4 reply threads
The support post ‘reCAPTCHA not showing?’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.