|
poptheagency
|
October 16, 2017 at 6:14 am
A customer has booked two tickets for an event on our client’s site. In the WordPress admin it shows that the transaction is complete; this was payed through Stripe. However when we click on the name of the registrants for this transaction, the registrations show ‘Pending Payment’. When we navigate to the ‘Registrations’ page and search the customer’s name, we get no results.
The event in question had a limit of 18 guests, however our client ended up having two additional guests. This is because the two tickets weren’t added to the list of registrants.
Can you please investigate this and advise on what caused it and how to fix it in the future?
Thanks
|
|
Josh
|
October 16, 2017 at 10:56 am
Hi there,
May I ask is this happening with the current version of Event Espresso 4 and which payment method was used for the transaction(s) in question?
|
|
poptheagency
|
October 16, 2017 at 11:04 am
Hi Josh. The version version of Event Espresso is 4.9.44.p, so yes. The payment method is ‘Stripe’. Thanks
|
|
Josh
|
October 16, 2017 at 11:16 am
That’s actually an out of date version. The current version of Event Espresso 4 is 4.9.48.p. There have been more than a few bug fixes added to the plugin since 4.9.44.p.
|
|
poptheagency
|
October 17, 2017 at 3:09 am
Hi Josh, thanks for your reply. I have a few questions:
– Are these known issues/bugs?
– Could you please point me to a page where I can read about the bug fixes in EE 4.9.48.p?
– Will these issues be fixed and avoided in the future when we update to EE 4.9.48.p?
Thanks
|
|
Josh
|
October 17, 2017 at 10:18 am
There were a number of related issues fixed since 4.9.44.p and you’ll find those listed here:
https://eventespresso.com/wiki/ee4-changelog/
|
|
poptheagency
|
October 23, 2017 at 5:56 am
Thanks Josh. The issue occurred because the customer closed their window just after the Stripe payment was made and before the registrants were added to Event Espresso. We tested this after updating to 4.9.44.p; we got the same results.
|
|
Josh
|
October 23, 2017 at 11:49 am
May I ask was your site customized to move the registration step after payment? Normally the registrations are added before the payment step.
|
|
poptheagency
|
October 24, 2017 at 4:03 am
Hi Josh,
The registration step happens before payment. However the ‘Current Registration Status’ is updated from ‘Pending Payment’ to ‘Approved’ about 5 seconds after Stripe has accepted the payment. The problem occurs when the customer closes their window before the status change.
This is what the customer sees when Stripe’s accepted their payment: https://cl.ly/nGvg. This is a pop up iframe. Then the iframe’s removed and they see the loading gif on the page (https://cl.ly/nGyM), until they’re redirected to the success page.
We want to display a ‘Processing Registration’ message below the loading gif, after Stripe has accepted the payment. This could help prevent customers from closing their windows. Do you know a function from the that can be used to trigger this message? This would be a function from either of the Event Espresso or Stripe plugins.
Thanks
|
|
Josh
|
October 24, 2017 at 7:57 am
You’d actually use a hook from the plugin, then load your function via the callback on a hook, to add the message.
That said, Event Espresso normally displays this message after the payment modal is finished:
It seems that message is being hidden on your site. Do you have some custom CSS that’s targeting all messages from EE and setting them to
display: none?
|
|
poptheagency
|
October 24, 2017 at 9:24 am
Thanks Josh. Which plugin are you referring to? ‘Event Espresso’ or ‘Event Espresso – Stripe Gateway’? Also, do you know which specific hook we can use to do this? I can’t find any documentation on this. Could you point me to it?
Also, we removed display none for all EE messages, but we still don’t see the message you’re referring to. Is there documentation somewhere we can use to help with this? Do you know the specific CSS we need to display for this message?
Thanks
|
|
Josh
|
October 24, 2017 at 9:35 am
Hi there,
The code within the Event Espresso core plugin has two types of hooks: action hooks prefixed with AHEE_ and filter hooks prefixed with FHEE_. Beyond the built-in PHPdocblocks, there isn’t documentation for every hook within the plugin, and developers generally can find the hook they’re looking for by using a plugin like Debug bar + debug bar actions and filters.
You may need to step through the CSS that was added because by default the Event Espresso messages display unless otherwise hidden with CSS or by some other means of hiding them (someone could use jQuery too). One of the divs that’s used to display the messages on the front end has ID:
espresso-notices, so if your css has style rules for #espresso-notices those may be why you’re not seeing the message.
|
