Support

Home Forums Event Espresso Premium Concurrency control

Concurrency control

Posted: September 8, 2015 at 3:56 am


Jade

September 8, 2015 at 3:56 am

Hi there,

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?

I found this thread https://eventespresso.com/topic/oversold-ee-4-4-7/
where you mention rapid development of a timer back in May. Is this work complete?

Thanks,
Jade


Josh

  • Support Staff

September 8, 2015 at 11:02 am

Hi Jade,

It’s still a work in progress. If you’d like to test or keep tabs on its progress, the work is being done in this branch of Event Espresso core:

https://github.com/eventespresso/event-espresso-core/tree/BUG-8698-ticket-sellouts


Jade

September 8, 2015 at 7:37 pm

Hi Josh,

Thanks for the link.

So in the meantime, there’s nothing that can be done?

thanks


Tony

  • Support Staff

September 9, 2015 at 6:14 am

Hi Jade,

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.


Josh

  • Support Staff

September 9, 2015 at 6:15 am

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.


Jade

September 11, 2015 at 3:50 am

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!


Josh

  • Support Staff

September 11, 2015 at 8:18 am

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.


Jade

September 11, 2015 at 4:18 pm

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

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.

Event Espresso