|
Gonçalo Pereira
|
September 12, 2017 at 4:25 am
Hi,
In the last few weeks started to notice that some duplicated registrations where showing up in our events. At the same time we also noticed that the registration lists didn’t show the “Abandoned” transactions.
It turns out that the unfinished registrations as staying in the list as “Pending Payment” that is the default state. The only way of identifying this is expending the “session details”:
Abandoned:
Transaction Session Details
Registration Session 9df05e64e1798639d18d8a09e7aeed44
Transaction placed from IP
Registrant User Agent
Attendee Information : Complete
Payment Options : Initiated 2017-09-12 10:02
Finalize Registration : Never Initiated
Completed:
Transaction Session Details
Registration Session 9df05e64e1798639d18d8a09e7aeed44
Transaction placed from IP 195.85.221.94
Registrant User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
Attendee Information : Completo
Payment Options : Completo
Finalize Registration : Completo
How can we identify in the list the difference?
Thanks,
Pedro
|
|
Gonçalo Pereira
|
September 12, 2017 at 5:06 am
Hi!
I checked that the WP_CRON (EE_Cron_Tasks::expired_transaction_check()) was launched for both transactions but the abandoned registration stayed unchanged.
Thanks,
|
|
Tony
|
September 12, 2017 at 5:07 am
Hi Pedro,
Currently, the only way to identify those registrations is using the session details you mentioned above.
You could use this snippet:
https://gist.github.com/Pebblo/4910bcbd1da0819a9f1e712e62a5c5bb
To add a ‘Finalize Registration Step’ column to the CSV reports which will then show either ‘Complete’ or ‘Incomplete’ depending on the above.
You can add that to a Custom Functions Plugin on your site and then export the CSV to view.
Does that help?
|
|
Gonçalo Pereira
|
September 12, 2017 at 7:33 am
Hi Tony,
This change it’s a major concern for us!
We have a script running that manages the waiting list. If a record is unpaid after 4 days it cancels the registration to make room another one and notifies the primary attendee.
The abandoned registrations were excluded from the waiting list process by status and now, given the fact they are in the same state as the others that completed the payment process they are being notified when they are canceled, although they didn’t receive the initial invoice.
In the database model, where can we find the “Finalize Registration Step” and which codes/information should we use to filter this?
Thanks,
|
|
Josh
|
September 12, 2017 at 9:23 am
Hi Gonçalo,
I can recommend starting a github issue and label it with “Question”, then one of the developers can answer your questions about the database model.
https://github.com/eventespresso/event-espresso-core/issues
|
|
Gonçalo Pereira
|
September 12, 2017 at 9:30 am
Hi Josh,
Thank you very much for your information.
I will pass this information and me, or the developer of the script, will do as suggested.
Nevertheless, I believe that this is a downgrade in the registrations grid because we could identify easily who didn’t complete the registration and now they are mixed with those that completed the process…
|
|
Josh
|
September 12, 2017 at 9:36 am
Thank you for the feedback.
|
|
Gonçalo Pereira
|
September 12, 2017 at 9:41 am
Thank you.
|
|
Gonçalo Pereira
|
September 12, 2017 at 10:41 am
Hi!
I did as you suggested and I was told I should ask for the information here…
“nerrad commented 10 minutes ago
Hi Pedro,
This is the kind of question that is best posed in the EventEspresso support forums.”
|
|
Josh
|
September 12, 2017 at 10:50 am
Hi there,
I’m sorry for the trouble. Your question had little to no context so they didn’t understand what you were looking for, and incorrectly assumed it was a support question. What you’re looking for is really developer related since you’re looking for database models and code information.
I’ve reopened theyourissue on githup. Can you reply there and try to communicate exactly what you’re looking to do?
|
|
Gonçalo Pereira
|
September 13, 2017 at 2:52 am
Hi Josh,
Thank you very much. I have tried to describe ou need as accurately as possible.
If there’s anything more I could add, just ask.
Thanks,
Pedro
|
|
Josh
|
October 11, 2017 at 1:43 pm
This was fixed and the fix was included in the 4.9.47.p release.
|
