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 Can I Offer Different Tickets for Additional Attendees? | Event Espresso - Staging Server
We have our event setup to allow for additional attendees to be added. It asks for first name, last name and Email for each additional attendee but not what type of ticket they need. How can we set it up so the tickets are defined per attendee, rather than per order? Also, is there a way to do this just for a single event?
Standard registration uses the same ticket type for all attendee’s, in order to purchase multiple ticket types you will need to use the Multi Event Registration Add-on which basically allows you to add events to a ‘cart’ like system, select the ticket qty’s then checkout the multiple ticket types in one registration.
However once this is enabled it will be enabled for all events, the event list by default will display ‘Register’ and ‘Add to cart’ for all events. You could modify the event_list_display.php template to remove the link and just use a shortcode if you prefer.
EE4 is a totally different registration system but it does offer multiple ticket types within a registration as a part of core, however it is NOT compatible with any add-ons currently (including the Calendar)
Before moving to EE4 I would advise you to install a copy locally and see if will suit your needs.
That is not to warn off EE4 just that currently it may or may not suit your needs depending on your requirements.
Viewing 3 reply threads
The support post ‘How Can I Offer Different Tickets for Additional Attendees?’ 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.