Order properties missing after payment confirmation
I messaged Anders about this, but posting here too in case anyone else has input.
I've set up Stripe as the payment gateway - everything appears to be working fine with the payment, the order is finalised and saved, only thing is all the order properties are missing (name, address etc). The cart details are saved, but not the customer details.
At first this seemed intermittent, but now appears to be doing it every time. Although everything about the payment seems to be working (payment all looks correct on Stripe, no errors there), in the logs there is this line.:
The problem was because Richard called the GeneratePaymentForm using the Razor API at the step where the customer types in the customer information. This locks the order for further changes. Then Richard updated the order properties using the Javascript API, but because the order was locked, Tea Commerce made a copy of the order and added the customer information on this new order. The old order without the customer information was the one that was locked and what Tea Commerce then finalized at the next step. So the "wrong" order got finalized, but it was because of the way the implementation was done. So be sure NOT to change the order after the payment form is generated :)
Order properties missing after payment confirmation
I messaged Anders about this, but posting here too in case anyone else has input.
I've set up Stripe as the payment gateway - everything appears to be working fine with the payment, the order is finalised and saved, only thing is all the order properties are missing (name, address etc). The cart details are saved, but not the customer details.
At first this seemed intermittent, but now appears to be doing it every time. Although everything about the payment seems to be working (payment all looks correct on Stripe, no errors there), in the logs there is this line.:
2016-09-01 09:43:20,994 [P4720/D2/T12] ERROR TeaCommerce.Umbraco.Configuration.Infrastructure.Logging.LoggingProvider - Form: stripeToken : tok_18oqn6LjEGHwewZy19Bh1P0W
Anyone have any ideas?
The problem was because Richard called the GeneratePaymentForm using the Razor API at the step where the customer types in the customer information. This locks the order for further changes. Then Richard updated the order properties using the Javascript API, but because the order was locked, Tea Commerce made a copy of the order and added the customer information on this new order. The old order without the customer information was the one that was locked and what Tea Commerce then finalized at the next step. So the "wrong" order got finalized, but it was because of the way the implementation was done. So be sure NOT to change the order after the payment form is generated :)
Kind regards
Anders
Cheers for your help on that Anders.
is working on a reply...