Posted: March 4, 2020 at 10:36 am
|
We are having an issue with an apparently orphaned transaction somehow being accessed and triggering a fatal error. This sends an email to the admin. The transaction can’t be accessed through any registrations. Would it be ok to just delete the transactions directly from the database or is this likely to cause more problems. It doesn’t appear to affect website functionality, but is more of an annoyance. phpmyadmin screenshot Thanks |
Hi, If you view the transaction in the WordPress admin, what’s the fatal error? |
|
|
This is from the notification email: WordPress version 5.3.2 Error Details |
Thank you. The code in question is trying to retrieve the primary registration related to the transaction, and the primary registration has apparently been deleted. You could also delete the transaction, but that could lead to more orphaned data if there are other registrations related to the transaction. So before you delete the transaction you could also check the esp_registration table to see if any other registrations belong to that transaction. You’ll check the TXN_ID column. |
|
|
Great! Thanks for the info. |
The support post ‘Orphaned Transactions’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.