dashCommerce

My installation of dashcommerce 3.0 doesn't seem to redirect to receipt.aspx when returning from PayPal. It just stays on the pdthandler.aspx page.

Has anybody encountered the same issue?

Did you check the error logs to see if anything was logged?

System.NullReferenceException: Object reference not set to an instance of an object.
   at MettleSystems.dashCommerce.Web.paypal.pdthandler.Page_Load(Object sender, EventArgs e) in C:\mettlesystems\code\open source\dashCommerce\Web\paypal\pdthandler.aspx.cs:line 98

 So far I've been using dashcommerce out of the box(web site only)... haven't set up the source code for debugging.

A.

Looks like you are not getting a transactionId back in the querystring - look for tx in the querystring. Also, the Request is logged so you can look for it in the error logs - but it's logged as INFO.

Make sure you have your pdt settings correct in the sandbox / live environment. But, so far, this appears to be something wrong on the PayPal side of things.

I've got 2 entries in the error log of type INFO, they contain no information.

The PayPal sandbox account that I was using had an unverified email address.  After verifying the email address, I now get in the error log:

INFO

tx=8RV84848JT300194Y&st=Completed&amt=3.00&cc=CAD&cm=ab7fc6b7-cc61-4dc6-bde0-a5ccac66bdf7&item_number=&sig=V99yKFkOCIdXBr3RxpjfxpHM%2bLx0UHb8iFhuSf0lepkDg%2bHK%2blYjGVjOXwcMxyyLbuuEK2zTCdE4MS4X8yTDQti6WaS1R1lQwmccAlbrTqthFogyqqomSivdvDeVZIzCeKXZvQECYg%2bY15u%2bCD%2b1iHIPArivOwRUY8jca3dcwtM%3d

and

ERROR pdthandler

System.Net.WebException: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
   at System.Net.HttpWebRequest.GetResponse()
   at MettleSystems.dashCommerce.Store.Services.PaymentService.PayPal.PayPalService.Synchronize(String content) in C:\mettlesystems\code\open source\dashCommerce\Store\Services\PaymentService\PayPal\PayPalService.cs:line 292
   at MettleSystems.dashCommerce.Store.Services.PaymentService.PayPalStandardPaymentProvider.Synchronize(String content) in C:\mettlesystems\code\open source\dashCommerce\Store\Services\PaymentService\PayPalStandardPaymentProvider.cs:line 175
   at MettleSystems.dashCommerce.Store.Services.PaymentService.PaymentService.Synchronize(String content) in C:\mettlesystems\code\open source\dashCommerce\Store\Services\PaymentService\PaymentService.cs:line 200
   at MettleSystems.dashCommerce.Store.OrderController.Synchronize(Object[ args) in C:\mettlesystems\code\open source\dashCommerce\Store\Controllers\OrderController.cs:line 612
   at MettleSystems.dashCommerce.Web.paypal.pdthandler.Page_Load(Object sender, EventArgs e) in C:\mettlesystems\code\open source\dashCommerce\Web\paypal\pdthandler.aspx.cs:line 113

 The INFO and ERROR appear 2 times in the log table for the same transaction.

I just thought I'd pipe in and say I am getting the exact same error. I was just testing that feature/functionality when I encountered the blank page, and searched here for other people's experience... and I guess I'm not alone!

 I'll let you know if I do find some fix or correction...

works fine today... I changed nothing.

Thanks admin/Chris? for the suggestion that it was a PayPal/sandbox problem.  I didn't spin my wheels for too long.  :)

A.

True, it does work today.

But the reason for the error still stands. Paypal sent a badly formed message in its response, and dashCommerce doesn't handle it gracefully.

I did some debugging, and in PayPalService.cs, line 292

      StreamReader responseStream = new StreamReader(webRequest.GetResponse().GetResponseStream());

This method is gronking when the response stream is badly formed. Perhaps should be wrapped in a try block or something. The problem is that since it is uncaught, the exception goes up the call stack, until it is logged.  Because the actual page loading code is bypassed, the user is displayed with a blank screen.

In order to provide the user with a less confusing (aka not blank) response from our dashCommerce website, we should catch the exception and at least tell the user something helpful... like providing a link to the homepage ;)

I agree. There are a few things that should be catched. There are allot of computer illeterate people out there using DC, so it's provider errors should be caught (if not configured in admin panel) and display a graceful response.

I looked at the code and I see what you are getting at. We can at least provide some information or a link, but if it fails to get a valid response from PayPal, there's not much else to do - too much relies on getting a response. In addition, if you have IPN configured, then that will usually get pinged first in my experience. Also, the production environments are much more stable than the sandbox environments.