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
Additional Attendee issues... | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Additional Attendee issues…

Additional Attendee issues…

Posted: February 10, 2014 at 9:37 am

Viewing 1 reply thread


Joseph Mullen

February 10, 2014 at 9:37 am

Is there a way to not require email info for the additional attendees but still have it required for the person doing the registering/purchase?

I’m also having another issue: Our client has a ticket called “Table of Ten ticket” where a single $1000 price is paid for a table of ten. The ten people need to be entered into the registration, which I assume the only way is through the “add more” button to list additional attendees. However it wants to charge an additional $1000 for each attendee. There are two specific tickets like this where they just want to be able to enter in the additional attendees and not have it charge per attendee.


Josh

February 10, 2014 at 10:15 am

Hi Joseph,

Both issues can be avoided by changing the event options for the event so that “Additional Attendee Registration info?” is set to “No Info required”.

Then you add additionaloptional name fields for the primary registrant in the questions manager and add them to a question group in the question group manager. After that, the “extra names” question group can be assigned to the “Event Questions for Primary Attendee” box in the event editor.

Viewing 1 reply thread

The support post ‘Additional Attendee issues…’ 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.

Event Espresso - Staging Server