Al Brookbanks

I wonder if it's something silly. In the file modules/plugins/paypal_commerce/hooks/class.cubecart.display_basket.alternate.php find: $("#checkout_proceed").attr("disabled", true); I think better code that may be more reliable across browsers would be: $("#checkout_proceed").prop("disabled", true);

Reading back it really sounds like the pay now button is being clicked twice still. On first click if it takes too long but the button doesn't get disabled and they click it again this will happen. The five seconds apart orders confirms this in my mind. How long does a customer wait before clicking the button again if the server is too slow processing the payment. Five seconds should about the right amount of time to lose patience. I've got Debys site cloned but infuriatingly PayPal sandbox isn't working right now. Ill try again later.

Ok I will. I need to try and find a whole day to look deep into this.

What is the confusion? The PayPal button says "Continue" and not "Buy Now". If the issue comes over confusion then is the confusion the above, something else and do you have any suggestions to improve it? PayPal moved away from being the final part of the checkout process to a middle part.

No I don't think so. We had a small number of merchants facing this issue. Since that patch only yourself and debyink are still reporting problems. I've cloned Debys store which I hope to test this afternoon. The patch relies on the skin accepting the new javascript to disable the pay now button on first click. I'll be looking at that first.

Sorry. My mistake. I'd lost track of versions!

The old version 1.9.3 didn't have the new code to prevent this issue.

So this must be a safari issue. Can I clone your store and test it in Sandbox mode? This issues doesn't seem to happen anymore to other merchants that did have the issue. So frustrating for you.

Are you still on 6.0.8? I'd really recommend upgrading if so.

How long ago did you purchase this? I'm sure Ian will get back to you soon. @havenswift-hosting You can contact here https://www.havenswift-hosting.co.uk/clients/contact.php

Yes please use SagePay-1.0.13.zip. It should be fine with PHP 7.2 but 7.4 would be safer.

This is difficult to quote for but so long as none of the files are encrypted I'm sure we can do it under our standard technical support.

Absolutely you can. Are the plugins encoded? If so then you are stuck. If not the code can be updated to work with PHP8.

You can upload the movie files to the files folder of CubeCart. Then create the product and select the file using the digital tab. That's all you need to do. CubeCart will send a unique download link after purchase.

I believe you but I need clues at minimum. Have any customers mentioned faults or unexpected behaviour? We found a problem caused by hitting "Pay Now" more than once. This has been patched. It's incredibly disappointing to see issues persists especially without any information as to how.

This issue is incredibly infuriating. I've spent hours trying to reproduce this on various devices coving as many scenarios as I can think of. It doesn't seem to affect that many merchants and those it does aren't able to reproduce it either. If I can reproduce this I can fix it. I'm desperate to get to the bottom of it as you are. Are there any errors in the request log with the order number in the body?

Great!!

Did it work?

It looks like there is a 3rd party patch: https://github.com/noelboss/featherlight/pull/412/commits/ddd0b99569072ce4dc5654f70cb634cfe902d919 We can try this via support if you need help.

This is the only issue I've seen concerning WEBP so far. If you wanted to open a support ticket I'm sure I can fix this for you. Sorry the update has caused problems for you. WEBP was only ever tested on the default skin.

I see. It's definitely failing to load in the image.

What exactly happens? I can't see why it wouldn't be compatible.

Lightbox shouldn't mind about the file format. Which skin is this?

Can you login to the extension configuration screen and click the disconnect button. Once done please connect again. Then save the config and clear the cache.

authenticationReason: ERROR is the clue. This means your customer has failed the security challenge set by their bank (not PayPal) and your PayPal Commerce settings are set to reject this scenario. Check your 3D Secure Scenarios in the module extension config page. In particular "Buyer may have failed the challenge or the device was not verified."