|
Brett McCumber
|
July 29, 2015 at 9:51 am
Hi there,
I searched through the forum but couldn’t find an answer to our problem. One of our events got overbooked by one person. We use coupon codes and paypal pro. We made sure student’s had payment status “completed”, last two bookings were booked about an hours apart, reservation time set to 10 minutes. So we have no idea how did that happen. Any ideas how we can prevent that? It’s crucial that event’s don’t get overbooked as we have to reschedule or refund anybody over the limit.
Thank you in advance.
|
|
Garth
|
July 29, 2015 at 12:54 pm
Hi Kat,
How are you today?
Can you describe your setup for us to better understand the scenario?
- What version of Event Espresso are you using?
- What payment method(s) are you using? It is possible that some gateways delay sending the payment notification to Event Espresso so that a seat may seem open when it should be booked.
One option would be to manually approve all registrations before they are allowed to make a payment and finalize their registration. I’m not sure if that will work for your events and audience or not.
|
|
Brett McCumber
|
July 29, 2015 at 1:09 pm
Hi Garath,
I’m good, thank you for asking.
We are using Version 3.1.37.1.P. And paypal pro. Tested and status changes simultaneously when payment processed.
We need people to be able to register and pay without our involvement. Otherwise there’s no point for us to use EE
|
|
Josh
|
July 30, 2015 at 7:25 am
Hi Kat,
Under normal conditions, an overbook should not happen hours apart. Do you have any caching mechanisms active on this server?
|
|
Brett McCumber
|
July 30, 2015 at 7:50 am
We have wordfence installed and it has caching enabled for faster web browsing experience.
|
|
Josh
|
July 30, 2015 at 4:25 pm
Can you disable the caching for the pages that handle Event Espresso’s checkout? They may be a little slower loading, but allowing Event Espresso’s checkout to load as designed (dynamically instead of from a cache) may then allow for accurate attendee counts and reduce the likelihood of overbooking.
|
|
Brett McCumber
|
July 31, 2015 at 9:16 am
Got it. And I added exclusions using this instructions:
Thank you for your help.
|
