Posted: August 9, 2018 at 5:47 am
I am slowing changing over all of our (hundreds) of events to utilise the multiple dates and tickets options to streamline the sheer volume of events we manage.
However I have stumbled across a little problem. Starting with our one-day workshops. There can be perhaps over 20 date times per event.
Previously, having one event/one date meant that they were nicely laid out in a table with each date on a new line and with a register button. Like this.
Now all the dates are together and there’s only one register button. It rather looks as though the registration is for ALL of the events, like this.
I think that is quite confusing for the customer and a bit off putting? Do you have a suggestion for how to handle?
The second part of this is related to long courses that have multiple dates as part of the same course. For these I have kept each house as a separate event or the number of date times on the course admin side would be monstrous.
However… the table layout of course shows all the dates like this, where as it would make more sense for it to show only the start date (the other dates are listed on the registration form).
Would it be possible for me to edit the table to show only the first date for these longer events without messing with the one-day events?
I know it’s complex. I’ve looked at a lot of your case studies and it seems we might be the only customer that I can see that has so many events to manage and so many different types. It’s a constant challenge between customisation and keeping close to the core plugin to get the most out of the features.
My suggestion is to not change the events over in this way. The multiple datetime/tickets feature is intended to be used for classes/events that meet at several times, where one ticket would give access to every time the class meets. Like a series of classes where you register once.
We do recommend keeping this simple, it doesn’t need to be made complex.
OK. I’ve gone back to basics!
Now I need to remove pagination and show the entire table on the template (not as short code). Can you give me a hint for that?
I’m a little confused about the meaning of “entire table on the template (not as short code)”, can you explain further and maybe post a link to the page in question so I can better understand?