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 Multiple Tickets with one User-Details | Event Espresso - Staging Server
Hello,
i have a problem with a multiple ticket-system.
i create an event and set in the
event option -> Additional Attendee Registration info? -> no info required
and set 3 price options
Adult 12€
Students/ Kids up 13 Years 9€
Kids free to 12 Years
And the problem is with this option.
The user must fill all selected options for a user-information with email. but why?
Is an option in which the user add only one ticket-information and all informations are on one ticket?
i am not an airline with personality tickets. For my business it is ok, when the user get one ticket with all informations with all registrated member-option (i.e.: 3 adults, 5 children, etc.).
I’m assuming you are using the Multi Event Registration Add-on (MER) to achieve this?
Unfortunately it is a limitation of the current system that each ‘ticket type’ much have at leave 1 set of personal information attached to it.
Viewing 1 reply thread
The support post ‘Multiple Tickets with one User-Details’ 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.