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
Moving development site to production server | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Moving development site to production server

Moving development site to production server

Posted: February 1, 2013 at 1:05 pm

Viewing 3 reply threads


Jim Ross

February 1, 2013 at 1:05 pm

I have reviewed some support docs and form posts on this. We almost have our development site ready to move to our production server. I have read you need to have your Site License Key reset when you move your site. But, I just checked and it appears I never added the Site License Key in the settings on the development site.

My question is do I have to have my Site License Key reset after I move the site if I never added it to the Development Site Key? If I have to reset it, what is the procedure to do that and how long does it take?

Thanks,
Jim


Jonathan Wilson

  • Support Staff

February 1, 2013 at 2:31 pm

Hi Jim,

You shouldn’t have to have it reset if it never was used. Just enter it on the live site.
If you have to have it reset, you can either let us know here and we will reset it for you, or click the “request reset” button in your account next to your license.


Jim Ross

February 1, 2013 at 2:55 pm

Thanks for the help Jonathan.

Jim


Jonathan Wilson

  • Support Staff

February 1, 2013 at 3:02 pm

You’re quite welcome.

Viewing 3 reply threads

The support post ‘Moving development site to production server’ 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