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
Export Excel/CSV has multiple wrong column headers | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Export Excel/CSV has multiple wrong column headers

Export Excel/CSV has multiple wrong column headers

Posted: August 17, 2012 at 11:50 am

Viewing 1 reply thread


ningram

August 17, 2012 at 11:50 am

On one event, when we export attendees in Excel or CSV, we get multiple instances of address, city, state (and other) column heads and some data is not in the correct columns. On other events, it works fine.

I can email the csv to someone if an address is provided.

Thanks!

  • This topic was modified 12 years, 5 months ago by ningram.


Josh

August 17, 2012 at 12:30 pm

Something similar happened with someone else where they had duplicated questions into two or more of the question groups (we think), so the events had many of these questions twice show up in the export. Check the questions and question groups that are assigned to these events. It might even help to compare the questions groups that are assigned to the events where the exports are correct.
Viewing 1 reply thread

The support post ‘Export Excel/CSV has multiple wrong column headers’ 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 12 years, 5 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server