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
more than one ticket for same atendee | Event Espresso - Staging Server

Support

Home Forums Translations more than one ticket for same atendee

more than one ticket for same atendee

Posted: April 18, 2014 at 7:11 pm

Viewing 1 reply thread


Daj Oka

April 18, 2014 at 7:11 pm

Hi,

I am demoing on demoee.org

I created a class with 10 “Datetimes.” (5 weeks, meets on M+W).

I created a discount bundle package for all 10 Datetimes. Easy enough.

From a previous post I understood that I can create a walk-up ticket with a “#Datetimes” of 1. If user purchases, say, 3 walk-up tickets, he can attend ANY 3 (three) of the 10 possible times.

The thing is, when I test a ticket purchase for 2 tickets for example, it wants info for 2 attendees.

How can I go about this the best way? Is the capability there to give options of multiple tickets-one attendee and multiple tickets-multiple attendees?

Thank you,
Daj


Lorenzo Orlando Caum

  • Support Staff

April 18, 2014 at 7:52 pm

Hi Daj,

Do you have question groups for additional registrants enabled? http://cl.ly/image/1r2W0N0m113C

If so, it will prompt for multiple registration information — otherwise, it should just use the primary registrants information.


Lorenzo

Viewing 1 reply thread

The support post ‘more than one ticket for same atendee’ 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.

Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.

Status: closed

Updated by Lorenzo Orlando Caum 10 years, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server