TOPIC: Paypal IPN Broken

Our site has been processing Paypal charges find and recently we had two cases, during which users reported "the site was broken" as they had problems registering. They offered everything worked fine until after the PayPal transaction. They advised that after registering they went back into their account and could not see the event they had registered for, but they had received the confirmation e-mail.

Our investigation revealed the following:

1. Looking in the Records in the back-end of DT Regiser, there was no registration present for the user recorded in the application.
2. When I logged into PayPal, I was able to confirm the transaction had successfully been completed and payment was received in our account.
3. When we tested the registration using PayPal we were in fact able to recreate the issue identical to what the user had experienced. What we noticed that the user did not tell us, is that when we did the test and clicked on the return to the site link, we received an unauthorized access message.
4. We went into the PayPal account and validated IPN was enabled, and that the return URL was to our homepage. We then setup a custom thank / confirmation page, and changed the URL in PayPal IPN configuration to the new custom page. Retested and still got the same results.
5. Checked the firewall settings and made an exception for cURL, retested and again the same results.
6. Tested and offline registration and everything went smoothly and the registration displayed in the record.
7. We created a manual registration for the two users, to satisfy their immediate need for confirmation.
8. When we performed a test on offline payment, everything operated correctly and we were able to see the registration record in the back-end immediately.

A ticket for this issue has been open since 7/19/2013; it has not been assigned and I have not received any follow up or response to the ticket or my e-mails, in which I offered to be fair and pay for your time if it was an error on our side. Our infrastructure support has already looked at the issue, and believes it to be an application issue. The ticket number is: TECH-2G21459320

My issues was resolve by the new 2.8.7 patch release, which Rich apprised me of today.

Many thanks!