I am using Opencart 3.0.3.2 with Payment Extension Paypal Express Checkout, by select Visa, Master or other card payment method. All installation and API set up looks not problem, but when click a credit card logo to proceed final checkout, a message shows as:
"Something went wrong. We'll take you back to checkout so you can try again.", with a Try Again button under it. When hit the button, comes up credit card info form as a Guest Paypal user.
Any idea how to get rid of the message to scare customer a the last minute? Any help would be appreciated.
"Something went wrong. We'll take you back to checkout so you can try again.", with a Try Again button under it. When hit the button, comes up credit card info form as a Guest Paypal user.
Any idea how to get rid of the message to scare customer a the last minute? Any help would be appreciated.
Download all files that contains 'pp_express' from my Github namespace: https://github.com/straightlight/opencart_contributions . This should resolved the problem.
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
Will this work also for OC 3.0.2.0? I have a problem with the PP Express popup window (1) requiring a second attempt (first says something went wrong) before payment is accepted and then (2) failing to close on completion of a successful payment.
Thanks
Martin
Thanks
Martin
Yes, this should work with all OC v3.x releases with the possible exception of the URL locations since the Github Master Branch version of Opencart namespace uses the language with their queries while the OC v3.x releases do not. This should not impact anything during the transactions with PP Express. See if that also rectifies the issue you are reporting about.
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
I have the exact same problem as the OP, the files you have linked to, do not fix the problem, but make it worse.
At the moment the problem is that an error message shows, although it's some what superficial, if you click try again, it will function correctly, but it's off putting to customers.
You new files, change the entire extention, turns off the responsive button and gives the old tiny traditional button, removes the card options (Well you don't need to change the files to remove the card options, you can do that already from the extention) We actually want the card functions to remain.
After all that the fixed files, the little PP button it leaves behind, actually breaks the PayPal entirely, so what was just a superficial error message for the card options only, turns the actual PP button into an error.
Error: Error: There was an error fetching the PayPal token at eval (eval at globalEval (https://www.mywebiste.co.uk/catalog/vie ... .js:2:2536), :14:21) at _loop (https://www.paypalobjects.com/api/checkout.js:779:46) at ZalgoPromise._proto.dispatch (https://www.paypalobjects.com/api/checkout.js:796:53) at ZalgoPromise._proto.resolve (https://www.paypalobjects.com/api/checkout.js:751:66) at https://www.paypalobjects.com/api/checkout.js:737:41 at XMLHttpRequest. (https://www.paypalobjects.com/api/checkout.js:1092:24) at Object._RECEIVE_MESSAGE_TYPE. [as postrobot_message_response] (https://www.paypalobjects.com/api/checkout.js:4247:27) at receiveMessage (https://www.paypalobjects.com/api/checkout.js:4278:48) at messageListener (https://www.paypalobjects.com/api/checkout.js:4297:9)
So a fix to the old extention, to stop that little error message showing in the screenshot, rather than changing the extention to a dud one.
At the moment the problem is that an error message shows, although it's some what superficial, if you click try again, it will function correctly, but it's off putting to customers.
You new files, change the entire extention, turns off the responsive button and gives the old tiny traditional button, removes the card options (Well you don't need to change the files to remove the card options, you can do that already from the extention) We actually want the card functions to remain.
After all that the fixed files, the little PP button it leaves behind, actually breaks the PayPal entirely, so what was just a superficial error message for the card options only, turns the actual PP button into an error.
Error: Error: There was an error fetching the PayPal token at eval (eval at globalEval (https://www.mywebiste.co.uk/catalog/vie ... .js:2:2536), :14:21) at _loop (https://www.paypalobjects.com/api/checkout.js:779:46) at ZalgoPromise._proto.dispatch (https://www.paypalobjects.com/api/checkout.js:796:53) at ZalgoPromise._proto.resolve (https://www.paypalobjects.com/api/checkout.js:751:66) at https://www.paypalobjects.com/api/checkout.js:737:41 at XMLHttpRequest. (https://www.paypalobjects.com/api/checkout.js:1092:24) at Object._RECEIVE_MESSAGE_TYPE. [as postrobot_message_response] (https://www.paypalobjects.com/api/checkout.js:4247:27) at receiveMessage (https://www.paypalobjects.com/api/checkout.js:4278:48) at messageListener (https://www.paypalobjects.com/api/checkout.js:4297:9)
So a fix to the old extention, to stop that little error message showing in the screenshot, rather than changing the extention to a dud one.
Attachments
ppexpress.png (93.58 KiB) Viewed 2395 times
Using a custom theme, such as Journal?
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
Who is online
Users browsing this forum: No registered users and 2 guests