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
"No Primary Key" error when trying to import | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › "No Primary Key" error when trying to import

"No Primary Key" error when trying to import

Posted: April 7, 2014 at 1:36 am

Viewing 3 reply threads


Travel Greenest

April 7, 2014 at 1:36 am

I am having my site reworked on another server, and I exported my events from the original site into a csv file. When I try to import that csv into the reworked version, I get a page with this error message:

“There is no Primary Key defined on model EEM_Term_Relationship,” following by a string of characters and numbers with “GETPRIKEYFIE” in it.

What does this mean, and what’s the fix?


Dean

  • Support Staff

    •

April 7, 2014 at 4:09 am

Hi,

Is this an EE4 export to EE4 import? Or EE3 to EE4?


Travel Greenest

April 7, 2014 at 9:25 am

EE4 to EE4.


Josh

April 8, 2014 at 10:17 am

Hi Travel,

In cases where you want to move data from one server to another I’d recommend using a plugin like WP Migrate DB. This will copy over all the database tables and make sure the paths are correctly migrated from the other server.
Viewing 3 reply threads

The support post ‘"No Primary Key" error when trying to import’ 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 Josh 10 years, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server