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
Development server vs production server licence key | Event Espresso - Staging Server

Support

Home › Forums › Translations › Development server vs production server licence key

Development server vs production server licence key

Posted: February 25, 2014 at 2:38 pm

Viewing 1 reply thread


Tony Ucovic

February 25, 2014 at 2:38 pm

We’ve found in Plugin settings this note: “If this is a development or test site, please DO NOT enter your Support License Key. Save it for the live production site, otherwise you will unnecessarily run into issues with needing to have your Key reset.”

Wondering how could we else set up our events registration website (on development server) if we should not activate full version of the plugin?

Do we get a separate key just for development server?

Thank you!


Lorenzo Orlando Caum

  • Support Staff

    •

February 25, 2014 at 3:17 pm

I replied to your other post:

http://staging.eventespresso.com/topic/development-server-vs-production-server-licence-key-2/#post-82586
Viewing 1 reply thread

The support post ‘Development server vs production server licence key’ 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.

Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.

Status: closed

Updated by Lorenzo Orlando Caum 10 years, 10 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server