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
Cloned & Migrated site - Messed Up Event Espresso | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Cloned & Migrated site – Messed Up Event Espresso

Cloned & Migrated site – Messed Up Event Espresso

Posted: July 9, 2013 at 7:48 am

Viewing 2 reply threads


tdzl

July 9, 2013 at 7:48 am

Used WP Migrate DB to clone & migrate a site that uses Event Espresso. I have 2 separate licenses for each site. The 2nd site, however, seems to have retained some ties to the original site’s Event Espresso license. For example, when users register, the Invoice shows up with data from the 1st site’s license. Is there anyway to break the link to the old account without losing my event and it’s data?


Josh

July 9, 2013 at 8:58 am

Hi there,

If you cloned the site that will also clone all the settings stored in the wp_options table. While WP DB Migrate does a great job with migrating URLs and file paths, settings like mailing addresses on the invoice will need to be manually changed/updated on the cloned site. You can change what appears on the Invoice by going to Event Espresso>Payment settings and update the fields under Invoice Payment settings.


tdzl

July 9, 2013 at 9:03 am

Thanks, that worked! I was able to edit the PDF Invoice using your advice.

Viewing 2 reply threads

The support post ‘Cloned & Migrated site – Messed Up Event Espresso’ 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 tdzl 11 years, 6 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server