|
The Big Freeze
|
March 31, 2016 at 4:52 am
Hi! We’re running a family festival over 9 days, where we need ticket holders to book into a snow play session when they purchase their ticket. So 9 days x 16 sessions per day. Our key demographic is Mums purchasing on their phones or tablets, so we need it to be simple and streamlined.
This is how my designer has currently set it up, but there’s just too many tables per day. We really need one table per day that would be set out in 5 columns as follows:
Column A – the session times
Column B – adult ticket (can select quantity)
Column C – child ticket (can select quantity)
Column D – toddler ticket (can select quantity)
Column E – notification is the session is low on tickets or sold out
Is it possible to make a table like this and if not does anyone have any ideas how we can simply achieve what we need?
Thanks 🙂
|
|
Tony
|
March 31, 2016 at 7:22 am
Hi there,
With your event setup you can not use a single table without having multiple sets of tickets which may end up confusing for your users.
You could setup a single event, use multiple datetimes within that event (one for each session) and then create a group of tickets assigned to each individual datetimes. However it means yous users will need to select from 18 different tickets to allow you to monitor the registrations for each session.
How about displaying those events within a table using the EE4 Table View add-on? You can set each of those 6 ‘sessions’ you have now within a category, use the category_slug parameter on the event table view to pull in only those events then you users can select from each session.
When they select the session they’ll be directed to the individual ‘event’ and see the ticket selector for that specific session. Would that work?
|
|
The Big Freeze
|
March 31, 2016 at 2:21 pm
Hi Tony,
Thanks for your response. The Table View looks like what we already have. The problem is that with 16 sessions per day and each of these sessions having 3 different ticket prices (so 39 different tickets options per day) it needs to be streamlined. I’ve drawn a picture of exactly what I think will work. Is there anyway I can upload that here so you can see what I mean and let me know if it is achievable?
Thank
|
|
Tony
|
March 31, 2016 at 2:29 pm
Sure, you’ll need to host the image and post the link here. You can use something like dropbox, imgur or even just upload the image to your site through the media browser and then post the link.
We list some options available for screenshots here:
https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots
|
|
The Big Freeze
|
March 31, 2016 at 2:36 pm
Thanks Tony 🙂
So this is what we currently have (16 tables per day)
This is what I think would work better if we can make it. Each day would then have it’s own table. So first window would list all the days, then you click on which day you want and next window has this table to then purchase tickets for said session then you go through to payment.
|
|
Josh
|
March 31, 2016 at 4:31 pm
Hi there,
One way to streamline this is break out each timed session into its own event. This way they’ll first select the date and time in one step, then they’ll be presented with a simpler table where they only select quantities for each of the ticket types.
|
|
The Big Freeze
|
March 31, 2016 at 4:38 pm
Hi Josh,
Thanks for the ideas, but I think that is fairly similar to what we have designed here. The problem with having each of those tables in their own window is that each session only holds 100 people, so they sell out quickly. If someone wants to buy 10 tickets and they don’t find out there’s only 2 left in the session they’ve chosen until they click through, then it’s a lot of back and forth between windows. Busy mums HATE this. We really need to have something that they can get an overview and then select their tickets. Is there anyway to make something like the example I uploaded (this one) – our focus group responded really well to this design. Thanks
|
|
Josh
|
March 31, 2016 at 4:56 pm
I think you’ll find that a 5 column table won’t display very well on small screens. In any case, it will involve some level of custom development. Here’s a simple example of that shows how it can work to break up the date time selection, and show relevant tickets for that time session. This requires a bit of HTML and JavaScript development:
https://codepen.io/joshfeck/pen/WwZQyB
|
|
The Big Freeze
|
March 31, 2016 at 7:47 pm
Hi Josh,
Thanks for that. Would it work therefore if we did something like this:
Window 1
The 9 days – click which day you want to go to
Window 2
All the session times listed in one column and the second column says how tickets are going -> so either tickets available, tickets getting low, sold out. Visitor clicks on which session they want
Window 3
Customer Details
Window 4
Payment
🙂
|
|
Josh
|
March 31, 2016 at 8:49 pm
That’s pretty much how Event Espresso 4 works, the difference being in window two the columns are not displayed that way. A capable front-end developer could extend the ticket selector template to add the information to your specification though.
One of the developers listed on our pros page may be able to give you a quote on the cost of the custom development:
https://eventespresso.com/developers/event-espresso-pros/
|
|
The Big Freeze
|
March 31, 2016 at 8:50 pm
Thanks Josh – worth getting a quote 🙂
|
