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 keys triggering Event Espresso license key issue? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › ReCaptcha keys triggering Event Espresso license key issue?

ReCaptcha keys triggering Event Espresso license key issue?

Posted: May 3, 2013 at 9:44 am

Viewing 1 reply thread


David Rushton

May 3, 2013 at 9:44 am

I have been setting up my EE (v

I have the latest version of EE  and all plug-in are up to date.  I recently added the reCaptcha keys and it seems that they have triggered issues with my EE license key.

You have the correct Site License Key for Event Espresso but your current membership access only allows for automatic upgrades on one domain. Please log into your account to manage your Site License Keys or purchase a support license now.

I am getting five of these notifications including “Event Espresso”, Espresso Calendar, Espresso Permissions, Espresso Social & Espresso Ticketing.

Do I need a new license key? Seems to be the fix for others getting the same message.


Josh

May 3, 2013 at 9:53 am

Hi David,

I reset your key. What happens is when you save the Event Espresso>General Settings page, it will ping our servers to check the key, and the key may not have been entered correctly.
Viewing 1 reply thread

The support post ‘ReCaptcha keys triggering Event Espresso license key issue?’ 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, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server