Posted: October 12, 2018 at 12:33 pm
This is a continuation of the thread started 3 weeks ago:
I’ve now asked my hosting company to increase the length of URLs allowed.
I’ve used stripe connect, which appeared to go all the way through the process without an error this time. (Username and password accepted, final blue button clicked, no error messages).
But when I look in event espresso it does not say that Stripe is connected.
Instead the Stripe Connect button is still there:
When I do a test payment the same error as before comes up:
You did not set a valid publishable key. Call Stripe.setPublishableKey(). For more info see https://stripe.com/docs/stripe.js
Any suggestions as to how to proceed from here please?
Server issues aside, if you have a security plugin that’s actively blocking/filtering long URIs you could unset the option within the Security plugin’s settings that enables that feature. Or temporarily deactivate the security plugin(s) installed on the site, then try connecting to Stripe again.
If the underlying cause is a server limit, you can contact your host and ask then to raise the limit again. Under Apache, the limit is a configurable value, LimitRequestLine.
Are you convinced that the issue is one with long URLs which are blocking the Stripe Connect?
I did have a security plugin that was blocking long URLs, but I was able to switch off that feature. But it didn’t solve the problem.
My host did raise the limit on long URLs.
The support team emailed me to say:
Did they go about it the wrong way or did they not raise it enough?
Are you still getting a http error 414 when you try to connect the site, or is it a different error now?
No. This time no error came up.
The screen cleared when I hit the blue button without any error being displayed.
I assumed that this was a sign that it had managed to connect without error. But perhaps this is wrong since I’m not getting the “Connected” badge you spoke of.
But then when I do the test payment I get the “you did not set publishable key error” (see screenshot above).
Here’s what you’ll see when it’s connected:
If you do not see a checkmark with the word “Connected” next to it, along with a button that says “Disconnect”, that means your site is not connected.
Have you tried temporarily deactivating all security plugin, then go to the payment methods settings page, then connect with those security plugins deactivated?
OK that’s clear now.
So the connection isn’t happening, because I don’t see what you showed on the screenshot.
I sign in and EE Connect says I’ve successfully authenticated.
There is no error message, but yet it is not connected.
I have now tried deactivating all security plugins, but sadly it is not making any difference. It still happens exactly as I’ve described above.
Any suggestions as to how to proceed next?
I tried deactivating all plugins besides EE, but that didn’t help.
(There was a minor JS error, but it didn’t occur when I was doing the Stripe connect phase – Mixed Content: The page at ‘https://staging2.presencetraining.co.uk/wp-admin/admin.php?page=espresso_payment_settings’ was loaded over HTTPS, but requested an insecure image ‘http://staging2.presencetraining.co.uk/wp-content/uploads/2015/02/logo_icon_2-150×150.png’. This content should also be served over HTTPS.)
Any suggestions as to where to look next?
I don’t think your site will allow connecting to Stripe via the Connect API. What you can do instead is use the older method where you just enter your Stripe API keys in the settings.
The fields for those are removed in the newer version of the Stripe gateway, but you can restore them by adding this code:
You can add the above to a functions plugin. After adding the code, please be sure to activate the plugin on the WordPress > Plugins page.
Once those fields have been restored, you can follow this part of the Stripe set up guide:
The support post ‘Stripe integration error again’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.