problem with incorrect order information

[path2u]

I am hoping someone can assist me with this. we are running Oscommerce 2.2 on Linux, Fedora Core 2. We are having an issue that is causing us some real problems.

Multiple times now, although it definitely does not happen all the time, we are getting what appears to be duplicate orders. I will tell you what I am seeing as end result and ANY suggestion to track this down would be great. This started when customers reported getting email notification on purchases which they did not make, having another persons information in the email. It does not contain any CC info but you can understand how customers react to this type of situation. When I checked from within admin interface myself, found that somehow order was placed with incorrect customer number .... meaning I looked up the order number but the customer number did not match the person who actually placed the order. It appeared that maybe when someone signed up for new account while placing order something did not work correctly and they did not get a unique customer number, but instead were assigned someone else's so when order email is sent ... it was sent to email for THAT customer number. Wow, that explanation even sounds confusing to me ... ha ha.

Hopefully it is something someone understand, and can help with.

Thanks,

Jesse

[davidinottawa]

I am hoping someone can assist me with this. we are running Oscommerce 2.2 on Linux, Fedora Core 2. We are having an issue that is causing us some real problems.

Multiple times now, although it definitely does not happen all the time, we are getting what appears to be duplicate orders. I will tell you what I am seeing as end result and ANY suggestion to track this down would be great. This started when customers reported getting email notification on purchases which they did not make, having another persons information in the email. It does not contain any CC info but you can understand how customers react to this type of situation. When I checked from within admin interface myself, found that somehow order was placed with incorrect customer number .... meaning I looked up the order number but the customer number did not match the person who actually placed the order. It appeared that maybe when someone signed up for new account while placing order something did not work correctly and they did not get a unique customer number, but instead were assigned someone else's so when order email is sent ... it was sent to email for THAT customer number. Wow, that explanation even sounds confusing to me ... ha ha.

Hopefully it is something someone understand, and can help with.

Thanks,

Jesse

 

I've never had this problem myself - but have certainly seem many posts similar to yours.

It is usually a session id, sessions problem. Especially if you have the session id being displayed in the address bar and in turn this is being spidered and indexed by search engines.

 

this might get you started.

If it were me - I'd investigate purging the sessions table as well. As I say - I'vbe never had this issue - so I d on;t really know if this is possible or what the ramifications are.

 

Here's some light reading to get you started :

http://www.oscommerce.com/forums/lofiversion/i...hp/t175719.html

http://www.unitedforums.co.uk/vb/archive/i...php/t-4217.html

http://mysqldatabaseadministration.blogspo...p-sessions.html

http://www.oscommerce.com/community/contributions,2819

 

 

david

[path2u]

thank you for the starting place to look ...

it looks like some of those could definitely apply to our situation.

I have more into to add as well now,

it appears that what is occurring is:

sometimes when people place an order, we will get multiple orders with successive order numbers, each from the same person. For example:

I will get order number 919, 920, and 921 for the same 2 books from the same person.

They call me saying they definitely did not order the same 2 books 3 times in a row, however it will even go to

payment gateway ( usaepay ) that way. Luckily they ignore the duplicate in such rapid succesion, but it is still occurring from time to time.

I am going to attempt to apply the corrections listed and see what happens but I figured I would keep this updated.

thanks,

Jesse