We had major problems with overselling tickets with EE3 (up to 20 at times). We open bookings the day before the event and the sessions book out within minutes.
We did everything we could to reduce the impact by shortening the registration process and only allowing users to book 1 ticket at a time.
Can you tell me if there are any mechanisms in EE4 to avoid concurrency issues?
The other option would be to set the Default Registration Status to ‘Not Approved’ and manually update the status for the registrations as they come in which will likely not work in your situation.
In the meantime you can set the registration limit a bit higher than capacity and that can prevent overselling when many try to get the last remaining tickets.
Thanks for the suggestions Tony & Josh. But neither of these will work for us. The whole (strict) capacity of 60 book out within minutes – it’s not just the last few.
Hopefully this timer work is finished really soon!
It may actually be finished because we’ve run quite a few tests on it, then made some necessary adjustments that the testing revealed. It needs to go through a final round of testing before we can merge this branch to master.
That’s great news Josh. I’ve got another couple of weeks work to finish setting up and customising EE4 bookings before our events season kicks off. So I’ll check in after that to see how final testing is going.
Cheers
Viewing 7 reply threads
The support post ‘Concurrency control’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.