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 Best way to get a FULL export of event data? | Event Espresso - Staging Server
I’ assuming that the best way to get a full event data export is to export/import the tables using phpMyAdmin, however, when I do this it keeps telling me:
#1062 – Duplicate entry ‘1’ for key ‘id’
What is the best way to do the sql export/import process to avoid getting this error?
Well I first was looking at exporting the events_detail and then any others as needed. The table I’m importing into, however, is empty so that’s what I don’t get about the duplicate id error.
I tried using the events.csv from “export all event data”, but it was quite incomplete in transferring over info.
We have a new exporter under development that should be released with 3.3, which will allow customized exports, so you’ll be able to choose what gets exported.
As far as the error you are getting goes, I’m not sure why that would happen if you’re importing this into an empty table. From what I understand, that would happen if there was already a value for that key.
The support post ‘Best way to get a FULL export of event data?’ 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.