|
Meg Benedicte
|
November 10, 2016 at 2:06 pm
I’ve been using EE since EE3 was out and I have had a long standing issue with pending payments and I need a definite solution to the problem. Paypal IPN looks good as per the support documents, but can’t seem to figure out the problem.
Where do I start?
|
|
Josh
|
November 10, 2016 at 6:16 pm
I can recommend switching to the PayPal Express gateway. Since you already have a PayPal account, you can log into your PayPal account and get the API credentials in a matter of minutes. After you switch to PayPal Express, you’ll no longer be relying on the PayPal IPN to update transactions and you won’t see the pending payments statuses for transactions that actually paid.
|
|
Meg Benedicte
|
November 11, 2016 at 11:01 am
Thank you for your help. Here are couple of other issues that I have noticed,
1. I see Pending Payment message for both user types when payment doesn’t go through(paypal/hosting error) and when user changes his mind to not pay the fee and close the tab, but their information(first name, last name, email) is collected. How can I find the root cause?
2. I’ve registrants and events saved in EE dating back to 2013. How can I remove the past data and keep current years(2016) data to prevent any performance issues. I don’t see any archive functionality in EE dashboard.
|
|
Josh
|
November 11, 2016 at 11:50 am
You can check the transaction record (click on View Transaction if you’re viewing the registration) then click on “view additional transaction session details”. There you’ll see “Registration Step Progress” section that shows exactly how far the transaction progressed through the steps. For example if they stopped after submitting the registration form, then the last Completed step is the Attendee Information step.
Re: 2, There really isn’t a way to selectively remove data from prior years but keep current year data. There’s a utility that removes all data, which might be useful at the start of a new year or other breakpoint. Keeping old data shouldn’t cause any performance issues though.
|
|
Meg Benedicte
|
November 15, 2016 at 2:31 pm
problem solved. Thanks!
You should definitely add a new functionality to archive old data depending on the time line.
|
