Posted: June 14, 2020 at 10:39 am
I looked at this thread.
That ipv6 issue is exactly what I am seeing twice today after not noticing it before.
However, now I noticed that the contact’s email address was not captured in the course of this error.
Somehow the recovery from this IP address rejection from Paypal is causing EE not to store the contact email. So, the payment declined email never gets sent. That’s why I started noticing this issue today because my mail queue started backing up with empty email addresses!
Unfortunately, this is only going to come up more often as time goes by and until PayPal starts to support IPv6 there is nothing we (Event Espresso) can do about it.
Hmm, ok, so this is interesting.
The EE_Contact is saved to the database well before payments are initiated. It saves when you click ‘Proceed to payment options’ and before any of those payment options actually load the EE_Contact is saved with the details from the attendee information step.
I assume you’ve checked the EE_Contact itself and confirmed the email is missing?
The payment object (and the processing of it) doesn’t actually update the EE_Contact at all, its updates the payment object, which can then in turn trigger an update to the registration and transaction objects by afaik there’s no logic within the payment processing that would update an EE_Contact.
If you view the EE transaction for one of these registrations and view the additional session details (the link below the ‘Transaction Items’) what does it show there?