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
We only want one attendee information section for multiple tickets | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › We only want one attendee information section for multiple tickets

We only want one attendee information section for multiple tickets

Posted: March 11, 2013 at 2:54 pm

Viewing 4 reply threads


Secretary CTS

March 11, 2013 at 2:54 pm

If you set Group Registration to yes but additional attendee Registration Information to no, is it possible to have only see one Attendee information section (email and name) for all tickets you purchase for that event?

We have an event that has a primary ticket and meal ticket. Currently, each have a section, which is pre-filled, but we’d like to have just one. Is that possible?


Garth

  • Support Staff

    •

March 11, 2013 at 7:55 pm

Yes, you can choose what info you want to collect for the additional tickets: http://staging.eventespresso.com/wiki/create-a-new-event/#eventoptions

See the “Additional Attendee Registration Info?” section.


Ross Willits

March 12, 2013 at 8:41 am

I have read the linked instructions, but my experience is the same as the Original Poster. I can choose “No Info Required,” but if a patron purchases tickets at two different prices, they are asked for their name and info for each price selected.

Please see my test event here: https://www.steppingstonetheatre.org/programs/event-registration/?ee=87

If you add at least one ticket at each price point, when you go to enter Attendee Information, you are asked for info for Attendee 1, and Attendee 2. In the set-up, however, I have “No Info Required” selected.


Sidney Harrell

  • Support Staff

    •

March 12, 2013 at 3:25 pm

The “No Info Required” refers to the non-Multi-Event-Registration process only. If you are using the Multi Event Registration add-on and the shopping cart registration process and select multiple ticket types, then it will ask for info for the primary attendee for each ticket type.


Ross Willits

March 12, 2013 at 3:38 pm

Thank you for the reply.

If that is the case, it’s a dealbreaker for ticketed events for us. Good to know.

We’ll continue to use EE for our class registrations, where it works great, but it seems like there are too many barriers to using it for theatre events.
Viewing 4 reply threads

The support post ‘We only want one attendee information section for multiple tickets’ 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.

The original Forum description...

Status: closed

Updated by Ross Willits 11 years, 10 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server