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
mod_security and reCAPTCHA | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › mod_security and reCAPTCHA

mod_security and reCAPTCHA

Posted: August 13, 2013 at 7:45 am

Viewing 1 reply thread


Sue Peggs

August 13, 2013 at 7:45 am

Hi
We are getting a few bogus registrations so I read your posts on enabling mod_security and reCAPTCHA – I have checked with our hosts and they say that mod_security is enabled. I know this is not really an EE question but thought it may be a quick one for you to answer – is it worth my adding reCAPTCHA as well or can I assume that as mod_security is enabled these bogus registrations must be from humans? Many thanks.


Josh

August 13, 2013 at 8:14 am

Hi Sue,

I don’t think it can be assumed that if mod_security is enabled all the bogus registrations are from humans.

reCaptcha can be very effective to prevent automated bot-registrations, but there is a cost in that makes the registration form not as easy to complete for your customers. The decision on whether it is worth adding or not is really up to you.
Viewing 1 reply thread

The support post ‘mod_security 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.

The original Forum description...

Status: closed

Updated by Josh 11 years, 5 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server