|
Trojan
|
February 18, 2021 at 5:35 pm
For each event, we have multiple datetimes with associated tickets for each. We would like to use the waitlist feature but it appears like it is only available for the event level. Is it possible to enable the waitlist for the ticket?
Alternatively, is there a better way to use the EE system when our courses have multiple recurring datetimes. For example, some of our course have 4 classes per week and we need the course tickets to all show up on a single course page – we show tickets for approx 6 to 8 weeks into the future. Creating a separate event for each course and ticket would get onerous. Unless I am missing something.
|
|
Tony
|
February 19, 2021 at 3:29 am
Hi there,
Is it possible to enable the waitlist for the ticket?
Not currently, the waitlist add-on will only work on an event level as it stands.
Alternatively, is there a better way to use the EE system when our courses have multiple recurring datetimes….
The short answer here is EE4 does not officially support recurring events so separating them into individual events will be required.
Do users sign up for individual classes or the full course?
|
|
Trojan
|
February 19, 2021 at 1:31 pm
People sign up by individual classes – these are one-off safety training classes (we call them courses). Right now we create one event for each course and then create multiple datetimes with tickets for each datetime.
We need the available class dates to show up on a single page like it is here – is there a better way to achieve this? https://www.trojansafety.com/events/h2s-alive/
|
|
Trojan
|
February 22, 2021 at 3:35 pm
Any thoughts on this?
|
|
Tony
|
February 23, 2021 at 3:45 am
If you want to list all of the tickets in the above view, then yes they’ll need to be within a single event as you have them now.
You could separate them out into individual events, however, you’ll then need to display those events on another page first for your user to select the required date (the event for that specific date). For example, displaying them on the calendar or table view template although both add another step for your user to get through before registration.
Without creating a different registration flow in which you display all of the ‘EE events’ for a specific course I can’t think of a better way to implement this within EE.
You are going to run into an issue with using a single event with so many datetimes/tickets with the current version of Event Espresso in that you’ll hit your servers ‘max_input_vars’ limit which if set to the default of 1000 usually happens at around 20 datetimes/tickets. You’ll know when it happens as you’ll create a new datetime/ticket combo and then on save it will disappear and/or a modal will show in the editor showing you’ve reached the limit on your server. You can either increase the limit when it happens or personally, I would duplicate the event and change the title and slug of the original to include the date then change the slug of the duplicate to replace the original.
|
|
Trojan
|
February 24, 2021 at 1:06 pm
We have our limit set to 5000 but I see what you mean. So perhaps we would at the end of each month (or so) duplicate the event and save the original as an archive and label the event for example: “First Aid Course January-February 2021”. Then on the duplicated version, would we delete all datetimes that are before the current date? Will the system allow us to do this or will we need to remove all the registrations first?
Too bad there is no recurring event feature – that would make life super easy.
|
|
Tony
|
February 24, 2021 at 2:03 pm
The duplicated event will not have any registrations on it as they will be linked to the original. It will be a copy of the original with new datetimes/tickets copied into that new event, so you create the dupe and adjust the datetimes/tickets for that dupe to suit.
Note its not just the total you need to change, but also the event slug so that events can still link to the slug you use now and the archives have their own.
Too bad there is no recurring event feature – that would make life super easy.
We are working on it 🙂
We have redesigned the event editor to to prevent the issue with max_input_vars (we learnt from the current release that recurring events couldn’t work with it due to the above so that had to be done before any work on REM).
The pre-release for beta testing is due out relatively soon and then REM will follow (no ETA on that just yet).
|
