|
yondbee
|
November 15, 2016 at 10:27 am
Hi,
I have an event that repeat every day from Tuesday-Sunday, and in each day need to create 10 diferent ticket for diferent hours, each ticket with a limit of 2 persons, ex:
Tuesday:
– Ticket: 10am – 11am (limit 2)
– Ticket: 11am – 12am (limit 2)
…
Wednesday:
– Ticket: 10am – 11am (limit 2)
– Ticket: 11am – 12am (limit 2)
…
I try to find the best way to do it.
any suggestion??
thanks
|
|
yondbee
|
November 15, 2016 at 11:50 am
I can`t see other way to do it, but create an event for every day in calendar,
and inside each event create all the 10 diferent tickets-hours (10-11, 11-12…)
Because with the sistem of “Multiple Dates and Times” i can`t figure out how can the user choose a especific day and hour for purchase.
Any idea?
|
|
yondbee
|
November 16, 2016 at 2:46 am
Hi i started this topic but maybe i did not explain myself very clear, sorry about that.
https://eventespresso.com/topic/best-way-to-show-event-that-repeat-every-day-with-diferent-hours-day-tickets/
I try to figure ot if is there anyway to create a single Event, and inside this event create (with the Multiple Date system) different Event Datetime, one per day of year.
Next create lets say 10 different tickets (each tickets is a specific hour of the day). So in the end the user can purchase a specific hour (ticket) of a specific day (Event Datetime) All inside the same Event?
Thanks
|
|
Tony
|
November 23, 2016 at 8:21 am
Hi there,
Currently Event Espresso does not support recurring events, whilst it is possible to set up some kinds of recurring events with the current version they are often much harder to manage.
Each single ticket needs to assigned to a specific datetime (or multiple datetimes) in which the ticket allows access to (so the date/time in which the user is registering for)
So in your example with a single event you would need huge amount of datetimes and tickets:
(10 tickets per day) * (amount of days) = amount of tickets
Lets say your event recurrs for 1 year, so 365 days.
10 * 365 = 3650 tickets within a single event.
You then will need individual datetimes for each of those tickets so at least another 3650 datetimes.
This simply is not viable and will bring your server to a crawl each time the event page it loaded or a registration is made.
Also as you increase the amount of tickets the user must navigate through it becomes much more complicated for them to select the correct ticket.
One option is to break down the event into smaller events, say 1 event per week, create the tickets for each timeslot and the datetimes for those however even the small events will still contain a large amount of tickets due to each day having 10 timeslots.
|
