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 Getting lots of spam, is reCaptcha not working? | Event Espresso - Staging Server
Am getting lots of spam in the registration form, and reCaptcha is on. I do get an error if I test and do not fill it out. So how can these be getting through? They are all junk. Are actual people submitting these?
We had an event in September using this and had 80+ registrants, and no real spam, for a Dec event, got a few, now getting a lot, so seems to be getting worse. Are there other anti-spam measures being worked on or other things we can do.
Are others finding this?
Have had EE since last July, have the most up to date WP
From our end reCAPTCHA is working fine, we dont know of any issues with reCAPTCHA itself. And from some tests on your site it is working as expected.
It could be possible that the spam is from real people, it is fairly common and it’s generally the only way to get around the reCAPTHCA.
Have you checked your analytics to see where the spam users are coming from? Whilst it is a bit heavy handed, if the spam users are coming from China (for example) and you dont have clients from that way, you could just IP block the whole of China.
Viewing 1 reply thread
The support post ‘Getting lots of spam, is reCaptcha not working?’ 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.