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 Tickets & Passes for multiple events for a season | Event Espresso - Staging Server
Hi, I have a client that wants tickets for multiple events spanning across the summer season.
What is the best way about setting this up?
I’m thinking each multiple event “General Admission” should be a reoccurring event on a calendar.
1) General Admission in Nav has a Calendar on the page.
2) User then selects which day they want GA.
3) That should then take you to select which pricing option, child or Adult (View cart). Is this possible?
4) Continue shopping option? – User can then choose another multi event “a show” for 2 hours in the afternoon.
5) That should then take you to select which pricing option, child or Adult (View cart). Is this possible?
6) User then goes to pay for all events at once.
With Event Espresso 3.1 you could set up the events to go through the Multi Event Registration cart instead of the single event registration process. There is a detailed tutorial here that you can follow:
You could add additional event options in the form of additional [ESPRESSO_CART_LINKS] for events in the event description where this would be applicable too.
Viewing 1 reply thread
The support post ‘Tickets & Passes for multiple events for a season’ 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.