Steve,
I just tested this on my test portal and ite returning back fine from paypal on success and cancel. The cart does send the success and cancel url to paypal which takes precedence over what you enter at paypal in your account although you still need to enter the url to your site in your paypal account. Also you need to have a paypal business account in order for it to work. The following are some possibilities as to why the return form paypal is not working with your portal:

1. Firendly URLs are not enabled in your portal or you have a regex defined in your web config that is masking out the return from paypal

2. If you have ifinity URL Master installed there could be a configuration issue with URL rewriting

3. IIS/SSL Setup - you could have and issue with your IIS and/or SSL setup on your web server that is preventing the https return from paypal. Also, in IIS you can configure URL redirection and rewriting that could be the cause of the issue as well

4. Firewall - There could be a rule in your firewall that is filtering, blocking or changing the return url from paypal.

5. Paypal Config issue - Make sure you have a business or premium paypal account. The regular standard accounts dont work. Make sure your pp account is configured properly as per the post above from Kevin and also the pp doc.

Lastly, I would try setting up a new dnn sandbox and installing cart 4.38 on your desktop or laptop so you can see it working which should isolate the issue as being in the cart or your server/dnn portal setup.

---

Scott Kelly
Project Manager

The cart builds and sends the return url for paypal standard as follows:

url = String.Format("http://{0}:{1}{2}", Request["SERVER_NAME"], Request["SERVER_PORT"], EditUrl("Confirm"));
 

---

At your service,
Dave Smith

Request["SERVER_PORT"] will of course put in 443 because the BuyNow module is set to use SSL. We have a page setup called Marketplace, and in that we put the BuyNow module, and in the page "Other Settings" area, we have "Secure" checked, which means the buynow module will use the SSL certificate all the way through. For it to not to, PayPal would have to be isolated from SSL as a separate module, which cannot be done because it is all existing in the original BuyNow module. Or you just put in an override setting option, which would be used instead of building the server url with the port option. With that, you simply ignore the code you posted above, and just use the setting! Then all is solved!

I can't imagine I am the only one facing this... unless I have setup SSL wrong with the page the BuyNow module is on.

Note: you may not get many complaints because Internet Explorer wll partly register the return to the site, but the page will not be fully displayed. We first found out about this from a customer. Firefox completely freezes and does not return. So some sales are registered correctly in IE, but they are not in Firefox. Plus, the incomplete page does not look good. Users are presented with the browser warning about insecure items, etc., and some items are not displayed correctly.

Steve