Comments and changes to this ticket
-
rasseljandavid (at gmail) August 30th, 2011 @ 07:29 AM
According to my investigation this scenario happens when the following occurs:
Sample:
Current Order ID: 5Client 1 added a product in the 'new' cart but he didn't checkout yet because he is sitll browsing in the store(New current order id: 6), Meanwhile Client 2 Added a product into his 'new' cart and he checkout first before the client 1 does(New current id: 7) So if the system admin check the order id, it will look like it is been incremented by 2 since the order id 6 is already been reserved by the Client 1. I "think" this is just a precautionary feature to avoid colliding orders when we will have hundred-thousand clients ordering simultaneously.
Another thing to note is that whenever a client confirm an order it creates another empty record with the same sessionticket_ticket and user_id and an invoice_id with a value of 0(see attached). This record will be filled the next time the same client order an id.
-
expNinja August 31st, 2011 @ 05:48 PM
- Milestone cleared.
-
-
dleffler September 21st, 2012 @ 02:15 AM
- State changed from open to resolved
- Milestone set to 2.0.9
- Milestone order changed from 4 to 0
Doesn't appear to be occuring
-
dleffler March 21st, 2015 @ 03:45 AM
- Milestone changed from 2.0.9 to 2.3.4
Actually this only occurred with the authorizedotnet calculator and resulted from the calculator incrementing the invoice_id in its process() method immediately after the cartController->process() method had done so.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS