Callback issue with Custom Errors

Posted By BORNXenon Wed 8 Oct 2014
Add to Favorites0
Author Message
BORNXenon Marked As Answer
 Posted Fri 10 Oct 2014
Supreme Being

Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)

Group: Forum Members
Last Active: Mon 23 Apr 2018
Posts: 59, Visits: 291
Right, after much more digging and messing about with my test installation, I have found the issue.

It appears that if running in Integrated mode, I have the following issues with the payment system:

The checkout page goes off to the payment gateway as it is supposed to, the payment is made and the payment gateway returns to Callback.aspx.
The callback page, instead of confirming the successful transaction and redirecting to CheckoutComplete.aspx throws an unknown error. It is unknown because it never gets written to the logs. If CustomErrors is set to 'On' in the web.config file, then the customer gets shunted through to Error.aspx. If Customer errors are set to 'Off', the customer gets shunted to the Customer.aspx (My Account) page.

The customer never actually sees an Order Confirmation. As a result of this, we have had several phone calls and cancelled orders, one customer placed his order 3 times as he wasn't sure whether or not the payment had gone through.

Also, if running in Integrated Mode, I am unable to be logged into the backend and frontend at the same time. If I am logged in to the frontend as a 'customer' and the backend as Admin, any changes I attemt to make in the backend result in me being redirected to the frontend My Account page, yet in Classic mode, it works as it should.

The only issue I have with running in Classic Mode, is that the graphs don't work in the backend, yet work perfectly in Integrated mode.Crying
BORNXenon
 Posted Wed 8 Oct 2014
Supreme Being

Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)Supreme Being - (44,541 reputation)

Group: Forum Members
Last Active: Mon 23 Apr 2018
Posts: 59, Visits: 291
We are using SagePay as our payment gateway and we appear to have an issue with the callback page when Custom Errors are turned on in the web.config.

If we have Custom Errors turned on, when an order is processed through SagePay everything goes through correctly and Callback.aspx is loaded but redirects to Error.aspx, yet doesn't actually log an Error in the error logs.
If we have Custom Errors turned off however, it redirects to the Customers 'My Account' page as it is supposed to.

I thought at first that this was caused by attempting to update the Google Analytics Tracking, however, it occurs even after reverting to the original tracking code, (I took a backup of the file before changing it).

Also, after being redirected to the 'My Account' page, the basket is not cleared.

I have replaced the Callback.aspx and the EcommerceTracking.ascx and associated .VB files with clean copies from the download zip file in case something has inadvertently changed, however the issue persists.

Can someone look into this for me?
Wed 8 Oct 2014 by BORNXenon

Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse

Back To Top