Over the last couple of days SagePay servers (particularly their test servers) have been failing to respond reliably - error 404, 500 etc.
This causes an ugly xslt error, and I would like to redirect the user away to a page that says "try again later".
I have written an XSLTRedirect extension but how would I react to the ucommerce xslt error on calling the SagePay server in the Checkout? I guess the more general question would be how do you handle an xslt extension error within the xslt?
How best to handle a SagePay xslt error
Over the last couple of days SagePay servers (particularly their test servers) have been failing to respond reliably - error 404, 500 etc.
This causes an ugly xslt error, and I would like to redirect the user away to a page that says "try again later".
I have written an XSLTRedirect extension but how would I react to the ucommerce xslt error on calling the SagePay server in the Checkout? I guess the more general question would be how do you handle an xslt extension error within the xslt?
Cheers,
Simon
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.