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
EE Attendee export CSV has duplicate column headers | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium EE Attendee export CSV has duplicate column headers

EE Attendee export CSV has duplicate column headers

Posted: November 13, 2012 at 10:51 am

Viewing 2 reply threads


CyberInnovation.com

November 13, 2012 at 10:51 am

My problem appears to be similar to an earlier thread () – my CSV includes column headers that are being inexplicably duplicated while the corresponding columns of data are not so the headers and data are misaligned. Looking at the resolution to the earlier issue, the cause was due to duplicate questions. In reviewing my questions, I don’t see any duplicates so I am stumped. A sample of the CSV file along with screen grabs that list my current questions can be found here For the record, I have purged some columns of data for privacy reasons. You will notice that starting with the “Emergency Contact” field, the column headers begin duplicating. Any help you can provide is much appreciates!


Josh

November 13, 2012 at 5:54 pm

Hi there,

Which version of Event Espresso is currently installed on your site?


CyberInnovation.com

November 14, 2012 at 10:27 am

We are using version 3.1.20.P

Viewing 2 reply threads

The support post ‘EE Attendee export CSV has duplicate 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.

Event Espresso - Staging Server