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
How will attendee data change with EE4? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › How will attendee data change with EE4?

How will attendee data change with EE4?

Posted: February 12, 2014 at 11:38 pm

Viewing 1 reply thread


rcfc

February 12, 2014 at 11:38 pm

We’re going to be doing some programming to integrate EE registrations with our internal workflow, and I was wondering if anything will be changing in the way the data (like when you export attendees to a CSV) will be structured.

Thanks,
josh


Lorenzo Orlando Caum

  • Support Staff

    •

February 13, 2014 at 1:06 pm

Hello Josh,

I’ve completed a registration on a new install so I could get you some information on how this works in Event Espresso 4. Here is a screenshot of event check in page for the test event (spring festival): http://cl.ly/image/1f1y3Y0m2i3U

Here is a CSV file for the registrations for this test event (spring festival): http://cl.ly/3L3e1m231u1A

Let me know if you have any additional questions.

—
Lorenzo
Viewing 1 reply thread

The support post ‘How will attendee data change with EE4?’ 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 Lorenzo Orlando Caum 10 years, 11 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server