|
Aaron Claessens
|
April 8, 2015 at 9:08 pm
Any thoughts on how I would go about structuring this …
Required base pass
Add On Event A or B
Add On Event C or D
or (a seemingly reasonable alternative)
Event A
Optional C or D
Event B
Optional C or D
|
|
Dean
|
April 9, 2015 at 5:53 am
Hi,
The closest I can see to getting that structure would require EE4.
Set 5 tickets for the event, making one ticket required (the base pass) and limiting the number of tickets that can be bought in one go to 2. The user would still need direction to choose A/B or C/D though, as there’s no logic in the plugin that can limit that choice.
You could use the second idea and create two events both with a required base pass ticket and then either A/B or C/D tickets.
I can’t currently see any other alternatives for your particular set up.
|
|
Aaron Claessens
|
April 9, 2015 at 9:06 am
Dean
Thanks .. I think that I need to use the 5 ticket option with some explanation as I have to track enrollment in the C/D events.
Are you aware of any plans to add more conditionals to do this? I guess that this is more conference / festival than just events …
|
|
Lorenzo Orlando Caum
|
April 9, 2015 at 9:52 am
Hi Aaron,
You would be able to set a quantity for each ticket option that is created via the event editor in Event Espresso 4.
—
Lorenzo
|
