Al Brookbanks
-
Posts
6,679 -
Joined
-
Last visited
-
Days Won
125
Posts posted by Al Brookbanks
-
-
Can you check the request log for any errors?
One of two things are happening. A missing PHP extension causing a 500 server error or possibly an error sending the confirmation email.
-
Good luck! Please use the Downloads section under the file manager area of the back office to add your files first.
-
Yes this is totally possible. It's quite simple. If a product has a digital file linked to it via the "Digital" tab of the Add/Edit product page it will act as a digital product and if not it doesn't.
-
2 hours ago, Debyink said:
I'll keep my eyes on the orders and hopefully (fingers crossed) it's sorted.
As jasehead said though, it wasn't double clicking, customers all said after making payment they were returned to my store but there was no confirmation that payment had been made, no complete purchase button, just back to the basket page so they went through the whole purchase process again.
I haven't been able to reproduce that. It sounds more like a session problem.
-
36 minutes ago, jasehead said:
No, but only if you have one item. They can purchase again if stock is available. Or they may duplicate the order with missing items and not understand why items are now missing. If they are confused and can proceed with a duplicate order, some customers will click through again.
Any workaround would be considered a win if it stops duplicate orders through PayPal and refund losses from PayPal charges.
The disable button on your store seemed to be working already so I wonder if the issue is different on your store.
It would be worth fixing the JS error on your checkout however. See attached.
-
@jasehead I totally agree about a work around being a win but I don't think we need to.
@Debyink I've solved this on your store.
The JavaScript to disable the pay now button wasn't working due to the order of certain elements in your skin.
I will release a new version of the PayPal commerce extension that fixes this by delaying the PayPal JS code.
-
Just now, jasehead said:
Or that completely blocks a duplicate order from the same email address + product codes + delivery add
Sounds like a possible work around but not actually a fix. Probably not a bad feature to have anyway.
I just cannot get PayPal sandbox to play ball today. Infuriating on an already horribly complex situation.
-
Stock handling could indeed come into this. If you have stock to reduce on processing this shouldn't cause a stock level problem.
-
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.
-
1
-
-
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.
-
50 minutes ago, foz1234 said:
Due to SemperFIWebServices no longer being around and supporting my plugins, my CC is pretty much stuck on 6.2.5 and PHP 7.2
Just wondering if I can create a new temporary CC store in say https://mydomain/test folder, then upload a back from my main store, no need for customer details, I just want to see at what point/CC version my plugins break if indeed they do, trying to avoid killing my online store and needing to restore it.
SemperFIWebServices plugin's currently running:
SFWS Custom Foundation 5 Skin V3.3.0
SFWS Special Content Boxes V4.1.0
SFWS Homepage Featured Products V4.0.0
Site Messages v4.0.0
Asking to assess if this will actually work?
Your thoughts appreciated.
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.
-
7 minutes ago, Debyink said:
Al, I'm still having this problem and still loosing money due to the no refundable fees.
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?
Opayo (Form)
in Extension Discussion
Posted
It's funny. This is the first time I've ever seen this error.
It's failing on the function escapeshellcmd()
It's a hosting compatibility issues. Can you ask your hosting company?