|
twcassidy14
|
August 31, 2022 at 11:48 am
Currently have EE 4.10.38.p on our event platform on onlinececredits.com. Sometimes we run two tickets on one DateTime. Sometimes customers will only partially complete registration and back out before paying for their chosen ticket. And sometimes customers will choose the INCORRECT ticket and email us wanting to select the other ticket and complete that registration, but they can’t because they are hung up on the other ticket that is “Pending Payment”
Current default registration status is “Pending Payment”
1. Is there a way that we can make it where customers can come back and finish registering on a ticket that is “Pending Payment”? Pending Payment status currently directs customers to contact the admin for help. They get frustrated they can’t complete registration themselves.
2. Is there a way for customers who haven’t finished registration to choose another available ticket and complete registration? Right now, if they choose one ticket and don’t complete registration, they are hung up in “Pending Payment” status which requires they contact the admin to have this cleared so they can make another attempt on the correct ticket.
3. If a customer has not completed registration on a ticket and they are “Pending Payment” is there a way to automatically have them sent a “Payment Reminder” email instead of having to manually trigger one? This would help us increase final sales conversions.
Thanks!
Tim
|
|
Tony
|
August 31, 2022 at 3:10 pm
Hi Tim,
Can you link me to an event I can run some test registrations? Or create a new test event I can use so its separate from your ‘live’ events (set it to password protected and post the password here to prevent registrations).
I’d like to see what is happening on your site before I start answering this further as some of what you saying shouldn’t be happening (pending payment registrations should not require admin intervention and users should be able to start a new registration by selecting the correct ticket on the event and starting again).
|
|
twcassidy14
|
September 5, 2022 at 9:43 am
Hi Tony! Thanks so much for writing back. I am excited to troubleshoot this. I have created a test event that is password protected. Please let me know if you need anything else or need to see the back end of our settings in EE. Thanks!
Link to event: https://onlinececredits.com/events/live-case-consultation-troubleshooting-trauma-treatment-october-2022-2/
Password: testpendingpayment
|
|
twcassidy14
|
September 5, 2022 at 11:12 am
Screenshot showing “Pending Payment” user message:
https://onlinececredits.com/wp-content/uploads/2022/09/PendingPaymentRegStatus.png
|
|
Tony
|
September 6, 2022 at 4:12 am
Hmm, ok so the screenshot you included for pending payment registrations is not the default behaviour for Event Espresso, that’s from a custom function I created a while back here:
https://gist.github.com/Pebblo/10669adfeea322ade3d96a38857fb46b
That code must be active on your site somewhere, when I provide snippets I recommend using a custom functions plugin to store them, some people use the theme’s functions.php file.
For #3, not currently no, we don’t have automated payment reminder emails at this time.
So #1 and #2 can be solved by removing that snippet from your site.
|
|
twcassidy14
|
September 6, 2022 at 5:52 pm
Hi Tony, had my web developer remove that code snippet – looks good now, thank you! I am thinking he originally installed it to prevent our users from registering for a single event more than once. We have had occasions where someone will register (and pay) for an event, and then at some point later register (and pay) for that same event forgetting they were already registered.
Is there any other way to prevent a single user from registering for a single event more than one time, regardless of chosen ticket?
|
|
Tony
|
September 7, 2022 at 8:49 am
Is there any other way to prevent a single user from registering for a single event more than one time, regardless of chosen ticket?
The problem with this request is it conflicts with #1 of the original request.
To prevent the user from registering onto the event we need to compare the registration they have already and do something to prevent them from registering. Be that using the method that snippet is using or another, it will still prevent the registration if it finds a previous one so I’m not sure how else we could do this.
I could provide details on how to update that snippet so that it only removed the ticket selector from view if the users most recent registration on the event also had a status of Approved, would that help?
|
|
twcassidy14
|
September 7, 2022 at 12:05 pm
I could provide details on how to update that snippet so that it only removed the ticket selector from view if the users most recent registration on the event also had a status of Approved, would that help?
Yes, please provide an updated snippet so that the ticket selector for a customer is removed only if the most recent registration on the event (regardless of chosen ticket) has status of Approved – that would satisfy my requirement, thank you!
Tim
|
|
Tony
|
September 7, 2022 at 4:19 pm
On line 29 of my snippet is:
if( $registration instanceof EE_Registration ) {
Change that to be:
if( $registration instanceof EE_Registration && $registration->status_ID() === EEM_Registration::status_id_approved) {
That will remove the ticket sector when the latest registration for that contact on the event is set to Approved.
So you may also want to change the text displayed from line 30
|
|
twcassidy14
|
September 8, 2022 at 12:54 pm
Tony, we got this dialed in perfectly, thank you for your excellent and timely assistance! -Tim
|
|
Tony
|
September 8, 2022 at 1:14 pm
Awesome, I’m glad it helped 🙂
|
