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 Akismet and Recaptcha | Event Espresso - Staging Server
Hi,
I have a question on spam protection.
My site is protected by Akismet. Therefore, I deactivated Captcha for Event Espresso.
Is this correct??? or should I activate ReCaptcha??
Well its a personal thing, you can have one, the other or both. I personally dislike captchas, but I know they are effective at stopping automated spam, but do nothing to stop manual spammers (people being paid to sit there all day and spam sites). I find Akismet to be very effective, though occasionally too effective.
Thank you for your prompt answer Dean. I understand from your answer that Akismet IS working inside event espresso too isn’t it?
So possibly I will try to start with Akismet-only and if I get spam members with unresolved payments I will set the recaptcha. Our event is not free, so I think there is no point in registering, you cannot leave any link or anything in the registering system, so I don’t expect spammers there.
To be clear: Akismet hooks into the WordPress comment system to filter spam comments. Event Espresso doesn’t do anything with comments and therefore Akismet and reCAPTCHA have nothing to do with each other with regards to event registrations.
This reply was modified 12 years, 2 months ago by Chris Reynolds.
This reply was modified 12 years, 2 months ago by Chris Reynolds.
Viewing 3 reply threads
The support post ‘Akismet and Recaptcha’ 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.