|
drkings1
|
September 18, 2018 at 11:20 am
Hi there,
I’m trying to integrate Event Espresso with Stripe.
Stripe is in test mode and the yellow test mode flash comes up on the payment screen.
When I put one of the test credit card numbers into the payment box I get the following error:
https://screencast.com/t/aBGPhWXK
You did not set a valid publishable key. Call Stripe.setPublishableKey(). For more info see https://stripe.com/docs/stripe.js
I’ve tried this in normal mode and in debug mode, but I get the same error.
Can you help?
Thanks
Daniel
|
|
Josh
|
September 18, 2018 at 11:42 am
Hi Daniel,
You’ll need to connect your site to Stripe before you can use the integration. This guide outlines the steps to make that connection:
https://eventespresso.com/wiki/stripe-payment-gateway/#connect
|
|
drkings1
|
September 18, 2018 at 11:46 am
Hi Josh,
I thought I *had* connected the site to Stripe. (I did follow this guide)
Does this error suggest that the connection wasn’t complete?
I must admit that I got as far as putting in my username and password, which were accepted by Stripe.
Then I finally clicked the blue button, but the window went blank and stayed blank.
Assuming that this is the reason for the lack of connection, how do I finish the connection to Stripe, given the blank white window?
|
|
Josh
|
September 18, 2018 at 12:15 pm
You don’t need to assume in this case, you can go to Event Espresso > Payment Methods and look at the Stripe settings. If the site is connected, you’ll see a checkmark next to the word “Connected”, along with a button to disconnect.
A blank white window could be caused by a number of things. The first thing to try would be do the connection using another web browser.
|
|
drkings1
|
September 19, 2018 at 12:10 pm
Hi Josh,
I got as far as receiving a message saying that I had successfully authenticated.
https://screencast.com/t/fQK04GDVRY
I then clicked the final button to complete the process and got the following error:
https://screencast.com/t/TDpHo3lck116
Any advice or suggestions?
Thank you
Daniel
|
|
Josh
|
September 19, 2018 at 1:13 pm
The error at the bottom of your screenshot shows http error 414, which means the URL string was too long for the server to interpret. See also:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/414
If you have a security plugin that’s actively blocking/filtering long URIs you could unset the option that enables that feature. Otherwise you can contact your host and ask then to raise the limit. Under Apache, the limit is a configurable value, LimitRequestLine. If they can change this value to something larger than its default of 8190 it can support a longer request URI.
|
|
Tony
|
September 19, 2018 at 1:16 pm
Hi Daniel,
HTTP Error 414 is ‘The request URL is too long’, you’ll need to contact your host and have them fix this on your server.
|
