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 details for single Registration with multiple ticket categories | Event Espresso - Staging Server
When selecting multiple tickets, the Registration Form requires the input of info for more than a single Registrant, even if the event settings are made to not require this. Any workaround here to remove the need for additional registrant info?
Are you meaning when the registrant adds events to the cart?
This is because they are separate events and the information is required for all of those events.
I am referring to when someone adds multiple ticket categories for a single event. eg, someone wants to buy 2 Adult and 3 child tickets to a Concert. On the rego form, they are required to enter personal info for the first adult and the first child. I understand the importance of this if they were different events, but they are not.
Sorry that I misunderstood. I understand what you are saying now.
This is happening because, if there are multiple types of tickets, it’s programmed to show one form per type of ticket.
I will discuss this further with our developers to see if I can get a more clear answer on whether there is a way to eliminate the requirement for separate forms for multiple ticket types.
Viewing 3 reply threads
The support post ‘Multiple details for single Registration with multiple ticket categories’ 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.