Duplicate Orders when Checking Out with PayPal - VM 2.6.4

[hotrod]

As of Now.. it seems this has worked for me..

Ran an order in IE  9.0 which I was getting Duplicate orders from.. and it came thru fine.  I'll keep you guys posted on future orders.

[tophatco]

I am having the same issues with authorize.net, which also started about the same time as yours hotrod, and both of us are redirecting our sites from http://www.domain.com to http://domain.com.

I had been following your issue in the thread below.

http://forum.virtuemart.net/index.php?topic=123644.45

What is your domain alex2311?

I have authorize.net in test mode right now trying to recreate the issue, or see it happen myself.

[tophatco]

I have authorize.net in test mode right now trying to recreate the issue, or see it happen myself.

With authorize.net in test mode I was able to recreate the problem after 14 orders.  I was switching back and forth between Windows XP/Internet Explorer 8 and Windows 7/Internet Explorer 11 and the duplicate order occurred while I was testing using Windows 7/Internet Explorer 11.

I am going to try alex2311's modifications in test mode and see if it helps.

[tophatco]

I am going to try alex2311's modifications in test mode and see if it helps.

I still get double orders with alex2311's modifications.

[Robert_ITMan]

See my suggestions here: http://forum.virtuemart.net/index.php?topic=123644.msg425930#msg425930

[slammy]

Hi, we are on jml 2.5.22 and vm2.6.6 since 2 weeks now. We did have normal orders last two weeks. Yesterday, falling from nowhere, we get duplicated orders too (Standard Payment!). our order-frequency ist not as high like others here in the forum, so I will wait for the next orders to see what will happen! Can someone of u tell me if the duplication could be because the user hits "F5" for e.g or use the "browser go back" in the cart after finishing the order?

And because there is some discussion about ssl - a very tip from value for your SEO in my opinion: Don´t switch general ssl on a livesite for longer time if you are actual on http with https in sensitive areas and only want to do tests! You will loose your best-ranking URLs - because the same URL with http or https is interpreted as a different one by google! That means, that google will exchange your best ranking URLs with the new ones. I really know where I speak about and we suffering from it since more than 6 month, because we switched completely from http and https in cart and account to full complete https. Since we did that in November 2013, we lost lot´s of nice ranking URL´s and it took us some time to get again near. We haven´t reached old rankings until today!
regards jens

[tophatco]

See my suggestions here: http://forum.virtuemart.net/index.php?topic=123644.msg425930#msg425930

Just to follow up on my experiences since I last posted on this problem.

Hoping to rule out the SSL cert, I bought a different one from a different vendor. We also had a different domain name we wanted to move the entire site to as well.  So with the new SSL, which was not limited to just the domain.com without the www, I put the site back up at www.obxskeeterbeater.com

Since then.  We have started running radio ads and the orders have picked up some. Not only are double orders coming in with authorize.net, they are also coming in on Paypal orders as well. The double authorize.net orders will double charge if the authorize.net plugin is set to Authorize and Capture.  The Paypal orders will go into VM twice, with only one being Confirmed.  The second will be stuck as Pending.  It looks to me that both Paypal orders are going in to VM but only one is being charged with Paypal because the visitor is only visiting the Paypal system once to make a payment.  When both Authorize.net orders go in, both get charged because they are set to Authorize and Capture and does not require the user to go through the charge process for each order.

I have set authorize.net to just Authorize and not Authorize and Capture so visitors do not get charged twice... but I must log in and manually capture the funds in the authorize.net merchant interface, and void the second transaction instead of capturing it if a double order went in.

When authorize.net double orders do go in, the buyer does get two order confirmations, but only charged once with the manual capture.  I don't want to confuse buyers who are getting two order confirmations though.  The Paypal double orders only send the buyer one confirmation because the second is stuck a Pending, which I delete from VM all together.

I am going to try your modifications next Robert_ITMan to see if it fixes it... although I don't think this is a user double click error.  I was easily able to recreate the problems in IE11/Windows 7 myself with authorize.net in test mode, and I wasn't double clicking. It could be a browser issue though and your fix may somehow resolve it so I will give it a shot.

It still seems to be only 1 out of every 10 to 15 orders doing this.  I will follow back up once I attempt Robert_ITMan's changes.

[oviliz]

That's truly crazy...

[hotrod]

I have proven, they are only coming from IE any version other than the newest.

[tophatco]

It still seems to be only 1 out of every 10 to 15 orders doing this.  I will follow back up once I attempt Robert_ITMan's changes.

Well, after Robert_ITMan's changes I still get double orders.  When you get hit the Checkout button, it disappears, you get the spinning arrow and please wait message... everything seems ok... but the orders still randomly go in double.

It almost seems like 2 carts are being created somehow and when the checkout process takes place, both are being checked out, even though there is only 1 checkout process for the buyer.

Now I have the submitted authorize.net orders go to Pending instead of Confirmed, so buyers do not get duplicate order messages.  With every order that is placed I must first log into VM, change the order to Confirmed so the buyer gets a confirmed order email and Cancel any duplicate order that may have gone in.  Then I have to log into authorize.net and capture the order and void any duplicates.  This way the buyer does not see the issue with duplicate orders if one is placed, but it's way too much to manage.

This is the only site I accept payments on so I am kind of stuck on what to do now. It isn't actually my site, I just built it for a customer, but don't want the customer to have to deal with the double order issue. I can't just keep correcting double orders every day manually though. I either sign up for a support subscription with VM and hope they address the issue, or look for another solution. Do you all think VM would be willing to help if I signed up? Or are there any third party developers/VM experts who I can pay to look at it?

[Milbo]

. I either sign up for a support subscription with VM and hope they address the issue, or look for another solution. Do you all think VM would be willing to help if I signed up? Or are there any third party developers/VM experts who I can pay to look at it?

We are after this error and already added some fixes to prevent sending of the form twice. Of course if you sign up the subscription, you give this task an higher priority and of course we need someone to test it and this bug is very nasty, cause not everyone have it. If you pay a 3rd party developer, the solution is either not in the core and so you have to add the fix if you are updating, or the developer spends it and I have to add it, spend time with it and so on.

[T.A. Garrison, LLC]

It's nearly a month later and Alex2311 seems to have the only answer.

I was just informed by one of my client's just today that they are seeing duplicate orders. I only found 4 in the last 3 months, which tells me that there are very few people who hit the button twice. But the fact remains, they get charged twice and it's extra bookkeeping...and time.

This particular site uses Authorize.net and "not" PP.
I implemented the resolve Alex2311 posted and I'm hoping it works.

So, Milbo. What's the update?

[oviliz]

+1

[Milbo]

It appears not only, because the people hit the button twice. And the fix to prevent that people hit the button twice is in there since vm2.6.2 at least. There is a js preventing that the button can be activated again.