You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When test mode is enabled and "cancel test orders" is enabled, it returns a null exception in the log file.
System.NullReferenceException: Object reference not set to an instance of an object.
at Pragmasoft.QuickpayV10.Extensions.Services.QuickpayV10PaymentMethodService.ProcessCallback(Payment payment)
05/14/2018 09:50:47: Exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at Pragmasoft.QuickpayV10.Extensions.Services.QuickpayV10PaymentMethodService.ProcessCallback(Payment payment)
05/14/2018 09:56:45: Exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at Pragmasoft.QuickpayV10.Extensions.Services.QuickpayV10PaymentMethodService.ProcessCallback(Payment payment)
05/14/2018 10:08:48: Exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at Pragmasoft.QuickpayV10.Extensions.Services.QuickpayV10PaymentMethodService.ProcessCallback(Payment payment)
05/14/2018 10:11:57: Order () was canceled because the payment was in testmode.
_logger.Log("Order ("+payment.PurchaseOrder.OrderNumber+") was canceled because the payment was in testmode.");
return;
}
The OrderNumber property on PurchaseOrder is null until the OrderNumber is assigned at last in the Checkout pipeline in the UCommerce core pipeline tasks.
Also I am not sure if OrderNumber is available here:
payment.Save();//Save payment to ensure transactionId not lost.
I think Checkout pipeline (or another pipeline) selected on the payment method first is executed on payment success callback, so if something fails in the payment, it doesn't continue to Checkout pipeline, where the OrderNumber by default is assigned.
When test mode is enabled and "cancel test orders" is enabled, it returns a null exception in the log file.
uCommerce.QuickpayV10/src/Pragmasoft.QuickpayV10.Extensions/Services/QuickpayV10PaymentMethodService.cs
Lines 78 to 85 in 9ec0dd6
The OrderNumber property on PurchaseOrder is null until the OrderNumber is assigned at last in the Checkout pipeline in the UCommerce core pipeline tasks.
Also I am not sure if OrderNumber is available here:
uCommerce.QuickpayV10/src/Pragmasoft.QuickpayV10.Extensions/Services/QuickpayV10PaymentMethodService.cs
Lines 98 to 101 in 9ec0dd6
I think Checkout pipeline (or another pipeline) selected on the payment method first is executed on payment success callback, so if something fails in the payment, it doesn't continue to Checkout pipeline, where the OrderNumber by default is assigned.
From UCommerce Basket.Checkout.config
The text was updated successfully, but these errors were encountered: