I've noticed (using the start kit) that the Tea Commerce will create duplicate orders for online payment providers.
I'm using version 1.4.2.4.
I've got two payment methods set up; default Account and online payment provider e.g. PayPal. I've noticed that if you select the PayPal payment method, or have it as default and cycle back and forth between steps 3 (Shipping/Payment) and 4 (Accept), Tea Commerce will keep creating new orders.
Below orders 141, 142 & 143 were created like this.
When you finally click on the Payment button on the Accept page, it will then create another order, 144 as it redirects you.
If you then navigate back to the cart manually without completing the online payment and go through the checkout process again, two more order will get created.
This happens for security reasons but maybe it shouldn't create so many copies :) Let me explain what happens and maybe we could find a better solution.
At step 4 we have the xslt function that generates the payment form. This function will also lock the order for further actions. This is because if you go to the payment gateway and then opens a new tab and browse to the shop and add another product - this should create a copied order with an extra product. The one you then pay at the payment gateway is still the one with just 1 product/order line.
The problem is that our security checks are too good and creates to many copies - or copies of the order - even though nothing is changed - so no copy should be created. We will have to look further into this "problem" to get rid of the many extra orders, But you can be sure that your system is secure and everything works for the customers right now.
I figured the reason was for the security of the transaction.
I am guessing the new order is created by the call teacommerce:GetPaymentForm($button) on step 4.
I think the reason I have not seen this behaviour before is because in my previous implementations (pure .Net) I generate the payment form seperately from step 4. My step 4 will usually contain a 'Pay' button which will redirect to step 5. The code on step 5 will then generate the payment form and automatically submit itself, so all the user really sees is the redirection to the payment provider and never actually sees step 5.
Maybe you could do something similar for the starter kit step 5 and it wouldn't then generate new orders every time you visit step 4. :)
Starter Kit creating duplicate orders?
I've noticed (using the start kit) that the Tea Commerce will create duplicate orders for online payment providers.
I'm using version 1.4.2.4.
I've got two payment methods set up; default Account and online payment provider e.g. PayPal.
I've noticed that if you select the PayPal payment method, or have it as default and cycle back and forth between steps 3 (Shipping/Payment) and 4 (Accept), Tea Commerce will keep creating new orders.
Below orders 141, 142 & 143 were created like this.
When you finally click on the Payment button on the Accept page, it will then create another order, 144 as it redirects you.
If you then navigate back to the cart manually without completing the online payment and go through the checkout process again, two more order will get created.
Should this be expected?
Hi Matt
This happens for security reasons but maybe it shouldn't create so many copies :) Let me explain what happens and maybe we could find a better solution.
At step 4 we have the xslt function that generates the payment form. This function will also lock the order for further actions. This is because if you go to the payment gateway and then opens a new tab and browse to the shop and add another product - this should create a copied order with an extra product. The one you then pay at the payment gateway is still the one with just 1 product/order line.
The problem is that our security checks are too good and creates to many copies - or copies of the order - even though nothing is changed - so no copy should be created. We will have to look further into this "problem" to get rid of the many extra orders, But you can be sure that your system is secure and everything works for the customers right now.
Kind regards
Anders
I figured the reason was for the security of the transaction.
I am guessing the new order is created by the call teacommerce:GetPaymentForm($button) on step 4.
I think the reason I have not seen this behaviour before is because in my previous implementations (pure .Net) I generate the payment form seperately from step 4.
My step 4 will usually contain a 'Pay' button which will redirect to step 5. The code on step 5 will then generate the payment form and automatically submit itself, so all the user really sees is the redirection to the payment provider and never actually sees step 5.
Maybe you could do something similar for the starter kit step 5 and it wouldn't then generate new orders every time you visit step 4. :)
Regards,
Matt
Hi Matt
Great idea - but I think we should address the underlying issue and only generate new orders, when the order has anything changed maybe.
Kind regards
Anders
Indeed, even better. :)
is working on a reply...