|
ryan randels
|
January 16, 2019 at 8:43 am
We had an event where people were chomping at the bit to purchase tickets. Our pre-sale was supposed to be limited to only 25 tickets, however 37 were sold. This was a large loss in revenue.
I followed all the respective guides preventing caching of certain pages, etc yet this still happened.
Here’s the setup:
Event Datetimes
Limit – 25
Sold – 37
Available Tickets
Type 1 – Qty 25, Sold 12
Type 2 – Qty 25, Sold 0
Type 3 – Qty 25, Sold 25
How can I 110% prevent this from happening in the future?
|
|
Josh
|
January 21, 2019 at 9:05 am
Hi,
May I ask which version of Event Espresso 4 was activated at the time? Also which payment method(s) were used for these transactions?
Since you’ve mentioned caching, which plugin(s) on your site handle the caching features?
|
|
ryan randels
|
January 24, 2019 at 4:34 pm
Hey Josh, for some reason I didn’t receive a notification, sorry for the delayed reply.
1. 4.9.56.p
2. Stripe
3. WP-Rocket with the following set to NEVER CACHE:
/registration-checkout/
/transactions/
/registration-thank/
/registration-cancelled/
/competitors/register-pro/
/the-event/volunteer/
/events/(.*)
|
|
Josh
|
January 24, 2019 at 5:03 pm
You’ll need to update to the current version of Event Espresso 4. The reason being is the 4.9.56.p version didn’t have all of the components of the ticket reservation system that have been added since that version was released. The ticket reservation system has features that prevent an event from overselling.
|
|
ryan randels
|
January 25, 2019 at 6:06 am
OK, thanks Josh. I’ve updated to 4.9.77.p and have my fingers crossed!
|
