|
MIAQC
|
March 1, 2017 at 11:51 am
I have created an event that has a variety of ticket options: member/nonmember rates; single and multiple day registrations; membership purchase; etc. How can I prevent the system for thinking it needs attendee information for each option selected? Currently, if someone wants to purchase a membership and a ticket to the event, the system wants to collect Attendee 1 and Attendee 2 info, even though the options selected are for the same person.
|
|
Tony
|
March 1, 2017 at 4:42 pm
Hi there,
The questions are set per event, so you can either collect information per selected ticket, or select a single set of information for all of the selected tickets.
One option would be to handle the membership outside of Event Espresso, so the user signs up for a membership on your site, which then gives them access to a reduce priced ticket using the EE4 User Integration add-on.
Would that work?
|
