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 Info for multipe price types | Event Espresso - Staging Server
All of my events have multiple price types, and I have ‘Additional Attendee Registration info” set to ‘No info required’.
When someone checks out with multiple price types in their cart, it still asks for attendee info for each price type. How do I get it to stop? I only want visitors to have to fill out their name and email once.
Each registration at each price type is considered a separate attendee (even if it’s the same person, which the system doesn’t know). So if you had group registration set to Yes and someone registered 3 tickets at Price Type A and 3 tickets at Price Type B, they’d get asked for their info twice (instead of six times). And the reason for this is because it needs to have some kind of information associated with the ticket that’s being purchased. Otherwise, in the attendee list, you’d have blank registrations with multiple tickets attached to them because someone registered for Price Type A and entered their information for that but also registered for Price Type B and didn’t. Does that make sense? The only way around it at this time is to use the Copy Attendee Info button which was backported from Event Espresso 4.0 to work around this issue.
It makes sense. Is this something that might get an overhaul in future cart versions? I think customers will find this functionality confusing and unnecessary, even if there is a reason in the backend.
Yes, this has had a major overhaul in the next version of Event Espresso.
Viewing 3 reply threads
The support post ‘Attendee Info for multipe price types’ 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.