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
EE4 Import CSV Example | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium EE4 Import CSV Example

EE4 Import CSV Example

Posted: March 20, 2014 at 5:55 pm

Viewing 1 reply thread


Andrew Havens

March 20, 2014 at 5:55 pm

I have been attempting to upload the CSV import file from EE3 but it simply errors out and says: The following errors have occurred:
The column titled event_name is invalid for importing. It must be be in the format of ‘Nice Name[model_field_name]’ in row 0,event_name,event_desc,address,city,state,country,zip,phone,display_desc,event_identifier,start_date,end_date,start_time,end_time,reg_limit,event_cost,allow_multiple,additional_limit,send_mail,is_active,conf_mail,registration_start,registration_end

No file seems to have been uploaded

Is there an example CSV file for EE4 so that I can change the format over to it?!?!?


Lorenzo Orlando Caum

  • Support Staff

March 20, 2014 at 6:17 pm

Hi Andrew,

You can create your own in minutes. Login to your WordPress admin and go to Event Espresso. Then create an event using the Event Editor — fill out as much content as you would like. Then save changes.

Go back to the Event overview page and click on the export button. It will then download a CSV file.

You can make changes to that file and then import through Event Espresso to see how it works.


Lorenzo

Viewing 1 reply thread

The support post ‘EE4 Import CSV Example’ 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