|
Michael Cain
|
June 15, 2016 at 6:12 am
Hi,
Getting slightly odd behaviour on my client’s website – we have a number of events set up to allow people to buy tickets / book places as mascots for football matches.
Each one has a cap of 10 tickets per package, and they have two ticket types in the event to choose from, with 3 tickets available as a premium ticket, and 7 as a standard ticket. Quantities have been set for each type.
Oddly, the quantity cap isn’t being enforced, so people have been able to buy tickets even if sold out.
Secondly, there seems to be weird issues with paypal returning abandoned payment messages yet taking the payment, so its proving to be an administration nightmare for my client.
Any advice?
|
|
Josh
|
June 15, 2016 at 7:30 am
Hi Michael,
The overselling issue is actually an issue with Event Espresso 4 core, but there is a branch that adds a ticket count/inventory feature that I install on your site that will correct that. Would you like me to install that on your site?
Update: The ticket count/inventory system is included in later versions of Event Espresso 4.9.
The other thing you’ll need to make sure to do if you have not done so already is contact WPEngine and ask them to disable caching for the pages that handle events and checkout, and also for them to enable the WordPress Heartbeat API. All of the details are in this support document:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
For the PayPal messages, I’ll follow up with an email and maybe you can reply with a few transaction IDs of the transactions where the abandoned payment messages were sent and we can investigate further.
-
This reply was modified 7 years, 3 months ago by
 Josh. Reason: updates
|
|
Michael Cain
|
June 15, 2016 at 7:37 am
Thanks Josh, speedy reply much appreciated.
I think installing the feature you mention is a good idea as we need to make sure the system is scalable for the client.
I did ask WP Engine to disable caching on the checkout as per documentation but I don’t recall asking them about the WordPress Heartbeat API but I shall get right on that now.
Drop me an email and I’ll supply you some transaction ID’s asap.
Thanks again
Michael
|
|
Josh
|
June 15, 2016 at 8:25 am
OK the branch is installed and activated, and I sent you an email.
|
|
Michael Cain
|
June 15, 2016 at 8:36 am
Thanks – received your email too, just getting the info together for you. In the mean time, WP Engine have confirmed that Heartbeat API is enabled, is there a way to test if it’s working or not?
|
|
Josh
|
June 15, 2016 at 4:01 pm
You’ll see the Heartbeat API script load when you view the source of the Thank You page.
|
|
Michael Cain
|
June 17, 2016 at 4:32 am
Thanks Josh – I’ve just emailed you the information about the transactions and all corresponding emails associated with them from Paypal and the website. I’ve also included instances of where the ticket limit hasn’t worked (pre-patch) and some other rather odd behaviour that has happened as a result. I look forward to your reply.
|
|
Josh
|
June 17, 2016 at 2:05 pm
Hi Michael,
I sent you and email with some recommendations based on what I could gather from the information that you sent. The events that have registrations that did not have a PayPal payment were set to have a default Registration status of Approved. So that’s why they would get the Registration Approved email without making a payment.
|
