Well, it’s been almost a month since my site stopped working (PayPal IPN not changing order status to Paid from Awaiting Payment even though PayPal says Sent and Status 200). I had some nice triggers working in 4.9 to unlock products and they still work in 5.2.3 but I have removed them for testing. I finally gave up on trying to fix my 5.2.1 DNN site or any upgraded version of it and went to a clean install of DNN 5.2.3 with Store 2.1.30 and it worked – until I configured my User Settings to: Redirect After Login, Logout and Registration; Use CAPTCHA for logins, and Registration; Require a valid profile for Registration, and Login. IPN then stopped working. I undid the changes and IPN works again. So I tried the same steps on my upgraded site (DNN 5.2.1 upgraded to 5.2.3). PayPal IPN is still not changing the order status as it should. I tried comparing the settings on my working portal (clean 5.2.3 install) with my broken upgraded portal (5.2.3 upgraded from 5.2.1) but I can’t get that portal to work no matter what I try. I have been working on this as time permits for almost a month now. Documentation was sparse on the upgrade so I am not sure if I should have upgraded to 5.2.2 along the way, but the install had no errors and the issue with the core DNN Subscribe link not going to PayPal was fixed (as expected). The only thing preventing us from rolling the site into production is the bug in the Store not changing the status to Paid via PayPal IPN. Both the working site and broken site are on the same versions of DNN and the store, reside on the same server, and hit the same PayPal account. The only difference is that the portal that does not work has 30 users each with Repository modules as well as a boat load of other content that will be difficult to move. It is also a Verified and the site that works is Public. Both sites are on a sub domain (mysite.mydomain.com) and PayPal IPN works on both sites with the DNN built in Subscribe link to PayPal. Why does the DNN core Subscribe link work with IPN to unlock a role but the Store site will not update the order status to Paid on the same portal using the same PayPal account? Why will the Store update the order status to Paid on a clean install only when there are no Redirect, CAPTCHA, or Profile changes made? Again, the DNN core works fine on an upgraded portal with these set but even a clean install of the Store on a clean install of DNN will not update the order status. Are there any known features or settings of DNN that do not work with the Store 2.1.30? I have removed SSL on the site that does not work and still nothing. I have installed and tested DotNetNuke Shopping Cart by DNNSpot and it does not work correctly with our sub domain, but their support was quick and they promised to have the issue fixed within a day or two. I am now testing Smith Cart but truthfully, I really like the way the Store module works. I just really need a fix so I can roll this project out. Any help would be greatly appreciated! As always thanks to Giles and other developers and contributors to the forum for a great product. If not for this one bug (and a few others I have seen unanswered on the forum lately) I would be highly recommending this product. Can anyone else duplicate my issue with Redirect, CAPTCHA, and Profile changes breaking IPN in the store module (see above for details)?

The issue I am having with PayPal IPN not working seems related to DNN Profile and User Settings which when set in certain combinations break IPN. I have tested on dozens of portals with several versions of DNN and Store with the same results. I am trying to figure out the code but I am a SQL coder and know little of web development. Any suggestions on how I might be able to fix this? It seems like lots of folks are able to run the Store without issue. Anyone using CAPTCHA or redirect on login successfully with the Store and PayPal IPN? This is still an open bug for at least a hand full of us. Thanks.