What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Bug - Unable to add Stripe which floats into top-left of toolbar.Asked by alixbryant on May 01, 2014 at 12:19 PM
I had a Stripe cart on my form, but somehow it dissappeared. Now I am unable to add it back.
I would advise to refresh your page. Do a full refresh (Zero Cache) by pressing CMD+Shift+F5 to your OSX Keyboard. I am not yet sure why the Stripe button appears to be on top of the header, based on your screenshot. I can't replicate it here.
Is it happening when you drag the Stripe button to the added fields section, especially on the header part? If you can still replicate the issue, please do so and check your browser console for the errors and let us know here so we can alert our developers, maybe that is a possible glitch. Anyway, no fields or features should be affected by this. I think that just when adding fields.
It does happen when I drag the Stripe button. I am actually trying to add it to the bottom of the page, but it keeps moving to the top.
I am using google chrome. I don't understand what "brower console" is.
The other strange thing is that when I click on "Integrations" Stripe does not show "connected" and I am unable to change it.
Thank You for the additional information. I have actually come across a similar issue with another field integration that had been doing that exact same thing in FireFox and Chrome about a week or two ago, but it was unrelated to Stripe.
I tested this also on my end to double-check it too as best I could but no luck here either. I believe there may likely be a bigger problem involved in the cause of it. So because of that I am forwarding a bug report about it to our developers this way they can look into it just in case.
We have just released a fix. Can you please try again and let us know how it goes?
it is working now. thank you very much!