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 question | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium reCaptcha question

reCaptcha question

Posted: January 27, 2014 at 6:25 am

Viewing 4 reply threads


B D

January 27, 2014 at 6:25 am

I would like to ask if, given that the mod_securiy module is activated (by default) with my webhost, I still need to use reCaptcha (which I would avoid, if possible).

Thank you in advance for your help.


Dean

  • Support Staff

January 27, 2014 at 6:35 am

A captcha system will not replace mod_security as mod_security helps to prevent XSS and injection attacks against a site. reCAPTCHA helps to stop spammer bot from posting (registering in this case).

They are quite different in what they do.


B D

January 27, 2014 at 6:48 am

Thank you Dean for this clear explanation.

So would you recommend installing reCaptcha with EE, or rather wait and see and possibly installing it later?

(My site will be live in a couple of days and if possible, I would spare the reCaptcha experience to my users. But if reCaptcha is strongly recommended, I’ll use it of course).

Thank you again for your help.


Dean

  • Support Staff

January 27, 2014 at 6:50 am

It’s up to you, some users don’t suffer from registration spam, some are inundated with it.

I think it would be safe to leave it off for now and if you notice an upswing in fake registrations to then enable it.


B D

January 27, 2014 at 6:52 am

Thank you. That’s exactly what I’ll do for the time being.

Kind regards

Viewing 4 reply threads

The support post ‘reCaptcha question’ 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.

Event Espresso - Staging Server