temparcweb

Got it—I will disable the legacy API. Thanks for the quick reply!

Thank you for your quick replies.

Yes, that’s true. Perhaps the option to redirect the customer to another page instead upon payment failure? I have had an issue with a site that does many payments that when the charge fails, the customer is not aware because they are still redirected to the success thank you page. The customer needs to know their payment failed.

For example, this is from the debug log of when a card is declined, the plugin will still direct people to the thank you page:

FAILURE: Your card was declined.
FAILURE: Error occured after user interacted with popup.
Redirecting to results page “/thank-you/”

It also follows the same steps for all other FAILURE errors.

@alexanderfoxc no problem! Just had to do some backwards compatibility testing on a site for a client and discovered the error ??

The new ES2015/2016 JS specifications are indeed not supported on IE11 or older Safari versions, you are correct. I anticipate there will be more and more issues like this at resulting from the fast pace JavaScript is developing every year.

Thanks for your quick responses and help to debug it!

Take care.

@alexanderfoxc This new version appears to have fixed the issue in Safari and IE 11. Thank you.

Thank you. I have reverted to 1.7.1 for now which is working in all browsers.

Thank you for your quick response.

I am still seeing the JavaScript error in Safari & Firefox on iOS. I am also seeing it in Internet Explorer 11 on a Windows desktop.

It does not appear to be resolved even after the cache has been cleared.

It appears there is a JavaScript error causing this. Below is the console output from Safari’s inspector on iOS:

SyntaxError: Unexpected token ‘=’. Expected a ‘)’ or a ‘,’ after a parameter declaration.

stripe-handler.js:61

@mbrsolution I just tested it and the custom amount problem appears to be fixed in the new version. Thank you for your help.

No problem – I will wait for the update. Thank you all for your help and for developing this plugin!

I have reverted to version 1.7.1 of this plugin (the last previous version I used before updating to the current version) and it does not have this error; custom amounts work with the above shortcode.

Thank you for your quick response. I’ve looked at the documentation but the same error occurs even with the shortcode provided in the documentation example:

Shortcode:
[accept_stripe_payment price=”0″ name=”Test donation for a good cause” button_text=”Donate Custom Amount”]

From the debug log:
[04/25/2018 9:14 PM] – Payment processing started.
[04/25/2018 9:14 PM] – Triggering hook for addons to process posted data if needed.
[04/25/2018 9:14 PM] – Checking received data.
[04/25/2018 9:14 PM] – Checking price consistency.
[04/25/2018 9:14 PM] – Getting API keys and trying to create a charge.
[04/25/2018 9:14 PM] – Firing pre-payment hook.
[04/25/2018 9:14 PM] – Processing payment.
[04/25/2018 9:14 PM] – FAILURE: Invalid positive integer

However, the normal shortcode buttons with fixed amounts where price=”XX” seem to work.