Posted: February 12, 2019 at 4:43 pm
I have the following use-case:
I’m adding tickets for each time slot (9:30 am Start, 10:30am Start etc….) but I’m trying to avoid creating a ticket per day.
Am I missing something?
In short, if you need to monitor numbers for each day you need that same set of tickets for each day.
If you have a set number of zips each day you can use 3 datetimes (1 for each day) and you can set an overall qty for the day on each of those, you’ll then need the same group of tickets for each day and you can set qtys on each session but you need to click the cog icon for each ticket and assign it to a specific datetime.
If the ticket qty’s don’t actually matter (looking at the event I’m guessing they do) you could have a dropdown question on the registration form asking which date it is for, then use the CSV export to sort them.
ah that’s a shame.
I actually simplified for clarity, there’s actually 7 sessions a day, each with 30 places. So that would be 21 options which is too many.
I think the best way would be to create an event per day and list them from the /events page.
On the Events archive page the template reverts to my post template, is that correct? How do I get access to the dates / location etc in the loop?
You could also use the DateTime filter feature:
When you have multiple datetimes on an event that are on different days you can use a dropdown to display the tickets for specific dates.
The archive will use
By default, EE will automatically inject the event details into that for you.
It depends on what you want to do, but take a look at
If you look in
Sorry for the slow reply Tony, that’s everything I needed thanks. Client is happy to go with an event per date (makes the listings look better haha).
Sorry, yes I meant archive template. That’s fine, I’ve dug all the template tags I need too.
Great stuff, seems to be pretty solid.
No problem, I’m glad you got it all working.