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
How to handle Site License Key for a test site? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › How to handle Site License Key for a test site?

How to handle Site License Key for a test site?

Posted: January 6, 2013 at 9:29 am

Viewing 1 reply thread


kstern

January 6, 2013 at 9:29 am

Hi, We have EE installed on our site, and upgraded to the latest version, which requires a site license key for setup. We are having some issues, so I was upgrading our test environment (on a subdomain of our real site) so I could do some troubleshooting. But I need a site license key for that installation as well. Do I just use the same one, or is there some other way to handle test installations? Thanks!


Dean

  • Support Staff

    •

January 7, 2013 at 1:43 am

Hi,

The licence key is for updates and support, so generally most people will have it on their test/development server and when the site is ready we offer a free licence reset to change it over. You cannot have the licence on more than one site at a time.

You can do two things though – as a developer you can use one of your other licence keys for the test site, or you can just manually update the test site.
Viewing 1 reply thread

The support post ‘How to handle Site License Key for a test site?’ 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 Dean 12 years ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server