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
Attendee export has duplicate columns | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Attendee export has duplicate columns

Attendee export has duplicate columns

Posted: February 15, 2013 at 12:46 pm

Viewing 1 reply thread


CyberInnovation.com

February 15, 2013 at 12:46 pm

Hello,

I had originally posted an issue that we were having with the exported column headers (http://staging.eventespresso.com/topic/ee-attendee-export-csv-has-duplicate-column-headers/). At the time, we were not on the latest version of EE. We have now updated to the latest version (3.1.30.7.P) but I am still seeing mismatched and duplicate column headers.

We have custom questions so this could be a contributing factor.

Thanks in advance….


Josh

February 15, 2013 at 3:45 pm

Hi there,

I’ve seen that happen with the roles and permissions add-on. Can you try deactivating R&P and do an export to see if that changes anything?
Viewing 1 reply thread

The support post ‘Attendee export has duplicate columns’ 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 ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server