|
A
|
July 2, 2015 at 12:06 am
Hi,
The IPN Validation is failing in Event Espresso 4.7.5. The problem started this evening in Event Espresso. 4.6.30 and the update to 4.7.5 does not resolve the problem.
Once the user completes payment in Paypal, Paypal shows that the payment is completed, but the payment is not approved in Event Espresso. The user gets a payment failed notification email and the Event Espresso transaction page reports the following error: An error has occurred! IPN Validation Failed! Paypal responded with ‘internal server error’ Error – read the server encountered an error or misconfiguration and is unable to complete your request.’ Then it assigns a reference number.
This is urgent as it is right in the middle of event registration. Please help!!!
There have been so many problems with Event Espresso lately, this plugin seems quite unreliable and it’s been very frustrating. I would appreciate a complimentary support ticket to fix this issue as soon as possible.
|
|
Dean
|
July 2, 2015 at 2:10 am
Hi,
We are also running into PayPal issues currently.
We think this is a PayPal issue, but I have raised an urgent developer ticket to look into it to see if there is anything we can do from our end that can help alleviate the issue.
One option would be to temporarily use an alternate payment provider.
|
|
Josh
|
July 2, 2015 at 8:24 am
We’re looking into this. It appears to be an issue at PayPal’s end. We’re looking to come up with a workaround and if we do, we’ll post more information here.
|
|
A
|
July 2, 2015 at 8:31 am
Could this have something to do with the email PayPal sent about a week ago re: dispute case tracking. See below:
If you are directly integrating data from the IPN process and/or the Case report into your systems, you will need to ensure that your configuration will accept the format change for the unique dispute identifier as outlined here.
Data passed contains a case_id value. This value will now be formatted in two ways:
– Existing format: PP-XXX-XXX-XXX-XXX
– New format: PP-D-XXXX
For the new format, XXXX is an integer. The “D” indicates the case is a dispute.
|
|
Josh
|
July 2, 2015 at 8:42 am
No because this isn’t an issue having to do with processing disputes, it’s an issue with the IPN when a payment is processed.
|
|
A
|
July 2, 2015 at 12:15 pm
Any ETA on when this might be resolved?
|
|
Josh
|
July 2, 2015 at 2:25 pm
Hi there,
We haven’t seen anything officially stated from PayPal about whether this has or hasn’t been resolved, and if it hasn’t been resolved yet, when. However, while working on things from our end, we found that the IPN validation is no longer failing. So it appears that PayPal may have fixed things on their end.
Are you still seeing an issue with the IPN validation failing?
|
|
A
|
July 2, 2015 at 2:59 pm
Hi Josh,
Thanks for looking into this. I decided to disable PayPal as a payment option for the time being. I’m following some of the other posts in the forum and it seems that people are still having issues with it. Please keep me posted when the issue is resolved.
|
|
A
|
July 2, 2015 at 3:04 pm
I’ve also had multiple users complain that they get kicked out of the Registration system before even getting to PayPal. They have to submit their registration information multiple times before even being directed to PayPal to complete payment. As I’m sure you can tell, it’s a frustrating experience for them. What could be causing this and how can we fix it?
|
|
Josh
|
July 2, 2015 at 4:06 pm
Caching will usually cause that. If you can give us some specifics about what’s happening when they get kicked out (eg. an error message) we can help.
As an aside, we might not get any official information from PayPal about what happened at their end, but we’ve been communicating with other WP plugin developers that also have PayPal integrations, and you’re welcome to follow the updates too.
https://github.com/websharks/s2member/issues/610#issuecomment-118140831
|
|
Lucas
|
July 2, 2015 at 11:07 pm
We spent most of yesterday afternoon working out this issue for bonnevillespeedtrials.com
Thank you for identifying the source of the problem. We’ll implement the work around shortly and start testing.
|
|
Josh
|
July 3, 2015 at 7:58 am
You may not need that workaround since PayPal has appeared to fix the issues at their end.
|
