Order Confirmation Processing Block .. vs duplicate orders

[lindasdd]

I think I have nailed this down to an issue where the processing time for Paypal is so long that every once in awhile someone will navigate away from the page, come back, and resubmit, before Paypal sends back the confirmation.

As a result, the cart isn't cleared and the customer is able to place a duplicate order.

Paypal says they can't speed up processing, so I'm wondering how I could change the 'submitonce()' functionality on the checkout_confirmation button to be a page overlay instead of just a button overlay.

There are a number of examples online, and this functionality is used in the Numinix Fast and Easy Checkout with Ajax module, but I'm trying to figure out a way to apply it to the standard template.

Any help would be appreciated.

[carlwhat]

seems like a lot of work.... have you tried:

https://www.zen-cart.com/showthread....76#post1317476

[lindasdd]

seems like a lot of work.... have you tried:

https://www.zen-cart.com/showthread....76#post1317476

Nice suggestion.

As a result I put this in place:
https://www.zen-cart.com/showthread....00#post1314200

It isn't a total page overlay, but it at least provides the customer a little more feedback by making the 'processing' image larger and visible even when the mouse isn't hovering over the button.

[badarac]

seems like a lot of work.... have you tried:

https://www.zen-cart.com/showthread....76#post1317476

Since implementing that on several client sites they no longer see the duplicate orders. Hope this works for you. Dr B you might want to think about increasing the time in a future update.

[carlwhat]

i'm a fan of removing the button after clicking it.

on another spot on one of my sites site i used the following jquery code to remove the button:

$(function() {
    $('#auth_button img').on("click", function (e) {
        $("#auth_button a").replaceWith("<img src='includes/languages/english/images/buttons/processing.gif' border='0' alt='Waiting' title='Waiting'>");
	});
});

button replaces with:



best.

[DrByte]

seems like a lot of work.... have you tried:

https://www.zen-cart.com/showthread....76#post1317476

Since implementing that on several client sites they no longer see the duplicate orders. Hope this works for you. Dr B you might want to think about increasing the time in a future update.

Willing to enterain a Pull Request.

i'm a fan of removing the button after clicking it.

on another spot on one of my sites site i used the following jquery code to remove the button:

$(function() {
    $('#auth_button img').on("click", function (e) {
        $("#auth_button a").replaceWith("<img src='includes/languages/english/images/buttons/processing.gif' border='0' alt='Waiting' title='Waiting'>");
    });
});

button replaces with:



best.

PR welcome.

[carlwhat]

Willing to enterain a Pull Request.


PR welcome.

when i get some time, i have a couple i need to work on.... very busy right now as moving primary client's payments over to cybersource.... but i hear you!

[carlwhat]

Willing to enterain a Pull Request.


PR welcome.

DrB,
i am looking at doing a PR for these things. what i was thinking was adding a variable to the configuration table for adjusting the timeout. in addition, i was also thinking about the replacement of the button with a moving gif similar to the one i posted earlier.

i am not sure the reasoning for having a 4 second timeout, as opposed to removing the ability completely to resubmit. but i'm sure there is a reason.

my question is how does one nicely get a variable into the config table for v160 (i know.... i should probably know how to do this...) and do you think that we should also add a config for completely replacing the button with a loading type of gif? or just do it and not allow users to change it?

thanks in advance.

[DrByte]

Don't over think it. Less is more :)
No need for a configuration switch: There's no need for a time-limit on the timeout. 4 seconds or 44 seconds it should be irrelevant: it's waiting for the page to reload.
Just replace it with a generically-named .gif ... that way if someone wants a different gif they can just replace the file without touching the js/html at all.