Errors on non-configured state and free products

  • Resolved tezalsec

    (@tezalsec)


    7 months, 3 weeks ago

    Hi, I am testing a new platform, and installed and activated your stripe plugin but not configured it yet. I am testing the checkout procedure first with free products before I actually activate payments. But the checkout page is giving me many stripe related js errors, complaining I haven’t set up my publishable key yet, and a “undefined” validation message.

    “IntegrationError: Please call Stripe() with your publishable key. You used an empty string.”

    “Uncaught TypeError: can’t access property “elements”, i is null”

    Should this not be handled more cleanly? When not yet configured, not give errors, especially when the order amount is zero so gateways shouldn’ t even be loaded?

    Same for your paypal plugin. JS Error here: “Error: Expected client-id to be passed (debug id: f914913ef5cee)”

    Thanks.

    • This topic was modified 7 months, 3 weeks ago by tezalsec.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Clayton R

    (@mrclayton)

    7 months, 3 weeks ago

    Hi @tezalsec

    Thank you for contacting Payment Plugins.

    Should this not be handled more cleanly?

    That is why the message is logged as a console notice and not a frontend notice. The console notice is for more advanced users that are troubleshooting integration issues. A customer is not likely to be using developer tools while checking out on your site.

    It’s a fine line when dealing with setup errors because another option would be to not enqueue the scripts if the plugin isn’t setup. But then we subject ourselves to support requests because merchants think there is a plugin issue if scripts aren’t loading.

    Kind Regards

    Thread Starter tezalsec

    (@tezalsec)

    7 months, 3 weeks ago

    I see what you are saying. Although as I did say there is also a on screen error validation message with text “undefined”. But to be complete, I can confirm though that finalizing the order is not being blocked by the errors.

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Errors on non-configured state and free products’ is closed to new replies.