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
Wordpress admin and front-end have two different URLS: do I need a new site key? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › WordPress admin and front-end have two different URLS: do I need a new site key?

WordPress admin and front-end have two different URLS: do I need a new site key?

Posted: January 2, 2014 at 6:05 pm

Viewing 1 reply thread


Cynthia O’Donnell

January 2, 2014 at 6:05 pm

I’ve been building a site at domain.com/wp for a while and had the key registered on the test site. I’ve now moved the front-end URL of the site to domain.com but the wordpress installation is still located at domain.com/wp

I requested a new API key since the front-end URL switched, but now I think that was a mistake… does the API key need to be registered to the front-end URL or the admin URL?

Thanks!


Anonymous

January 3, 2014 at 5:28 am

Hi Cynthia,

You license key has been reset. Please go to the wp-admin then Event Espresso -> General Settings.

Remove the key (cut) and save the options, replace the key (paste) and save the options once more.

That should solve the issue and Event Espresso will use the correct URL automatically :)
Viewing 1 reply thread

The support post ‘WordPress admin and front-end have two different URLS: do I need a new site 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.

The original Forum description...

Status: closed

Updated by Anonymous 11 years, 3 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server