|
Alex
|
June 4, 2019 at 10:19 am
https://eventespresso.com/topic/wait-list-sign-up-button-wont-appear-in-all-open-dates-of-the-same-event/
Has any progress / update been made on this? As posted in this forum link above, this feature would be super helpful to essentially “overbook” each section to ensure it is filled. We tend to normally have 1-2 cancellations for our classes up to the last minute and knowing there are people that we can quickly slot in because they are already on a waitlist (specifically for a certain DateTime) would be very beneficial! It seems from trolling around the forums here there was another workaround solution proposed ~3 years ago *PRE* EE4 waitlist plugin that involved a php code modification and use of ninjaforms. I don’t see why something like this couldn’t be adapted to work with the EE4 waitlist actual plugin (without need for NinjaForms).
https://eventespresso.com/topic/ee4-waitlist-for-events-with-multiple-datestimes/
|
|
Josh
|
June 4, 2019 at 11:14 am
Thanks for the feedback.
There has been no progress on this, and the reasons it’s not being picked up and changed to put waitlist forms for each datetime is two-fold:
1) Developer priorities. Currently the dev team is working on Recurring events for Event Espresso 4.
2) Web hosting/server constraints. We’ve found from experience that as the number of datetimes and tickets increase on a web page, with many shared hosting environments the page will slow down when loading up. This gets even slower as we add sold out status checks for each datetime. Since most of our customers are using shared hosts, we have to consider that constraint and be careful about what features to add when they’re resource intensive. In this particular case, adding waitlist forms for every sold out datetime could have the effect of slowing down the page load time significantly (instead of just one waitlist form for an entire event, which doesn’t slow the page down at all. So to add this feature in a way that won’t bog down most sites will require a complete rewrite/refactor of the way tickets for datetimes are selected. Which is something that would need to happen after the recurring events manager is finished.
|
|
Alex
|
June 4, 2019 at 1:23 pm
Hi Josh. Thanks for the thoughtful reply. I see your points and wonder if even a more informal solution [similar to what you proposed with Ninja forms] would still work here. I was just trying to avoid using another form plugin to create a simple waitlist form that could still be used to then manually “add” people to a course through EE if there is a cancellation/etc. In any case, I’ll likely attempt to re-purpose the ticket selector hook, which is how I am displaying my courses anyways per page, and see if I can come up with something. Just thought I could tie directly into the waitlist modal functionality somehow. Thanks in any case.
|
