Ticketpicker
This topic contains 5 replies, has 2 voices, and was last updated by 
-
Posts
-
Thanks for the recent fixes… I am now running the latest release of WPEO-PRO and enjoying the new features.
Regarding the ticket picker – (i am using the select menu version), is it possible to have a default selection option which shows all tickets?
Also – is it possible to output these as checkboxes?
Many thanks
Alex Steer
Hi Alex,
It’s not possible to display all tickets for all dates at once unfortunately. Each ticket type is in fact only rendered once, and it’s the combination of ticket type and date selected that determines what the user is booking for.
You can use checkboxes instead of a number input (see this page). If you want to restrict the user to booking only one ticket, you may want to see this page also: http://wp-event-organiser.com/blog/tutorial/limit-bookings-to-one-ticket/
Stephen Harris
Hi Stephen,
Thanks for the reply.
This is unfortunate because i would like to show all tickets then use the picker as a filter.
Regarding the checkboxes – I was meaning using checks instead of the drop menu date select.
The problem I found is that the calendar is too fiddly for mobile and my client doesn’t like the drop menu date selector… My idea to show all tickets would make the date selection UI elements complimentary rather than necessary.
Date selection is necessary, as a booking can only be for tickets associated with one date. That is, it is not possible to book places for an event on dates X and Y in the same booking.
Among other things, this allows for filtering of bookings by an event date on the admin screen.
Why this works for me is because I have a a date in the ticket title.
This could alternatively work by adding a date column in the table?Not easily I’m afraid. Tickets can be available on multiple dates, so in order for the plug-in to know which place is being booked it requires not just the ticket ID, but also the occurrence ID of the event. Even if you have only one ticket per occurrence, the plug-in doesn’t make that assumption.
So you would need to dynamically set the occurrence ID based on the user’s choice of ticket. (And then decide what should happen if the user selects Ticket A for occurrence X and Ticket B for occurrence Y).