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
Column headers in exported csv | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Column headers in exported csv

Column headers in exported csv

Posted: February 4, 2013 at 10:20 pm

Viewing 4 reply threads


Matt Sayre

February 4, 2013 at 10:20 pm

To produce an csv: Event Overview > Actions > Export to csv

The problem with the exported file is:
1) The column headers are not in the same order as the source event form.
2) Column headers do not match the corresponding data after column Z.


Chris Reynolds

  • Support Staff

    •

February 5, 2013 at 1:36 pm

Matt —

What version of Event Espresso are you using? I believe this was fixed in a recent update, but you might check to see if any of your event titles or questions have a comma in them and try removing the comma and replacing it (in the question) with ,.


Matt Sayre

February 5, 2013 at 4:56 pm

We are on Event Espresso – 3.1.30.1P

We will check for commas.


Matt Sayre

February 5, 2013 at 5:13 pm

Regarding the commas. Do the answers (to the questions) also need the comma substitution?


Dean

  • Support Staff

    •

February 6, 2013 at 5:32 am

Hi Matt,

Commas in the answers should not be an issue. Commas in questions should be fixed now, I would advise updating.
Viewing 4 reply threads

The support post ‘Column headers in exported csv’ 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 Dean 11 years, 11 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server