Can you please take a look at my form?

  • Profile Image
    Asked on June 08, 2011 at 09:11 AM

    We are using JotForm for our General Donation page. It's working great except that about 25% of people complain that the form doesn't work properly for them. I'm not a web guru, so I was hoping you could take a look at the form and make sure that everything I can do to make it safe and secure, I've actually done. Advice and input welcome. Thanks for your help!

  • Profile Image
    Answered on June 08, 2011 at 11:40 PM

    Hi mariciamit,

    Thanks for bringing this to our attention. Can you elaborate and describe further the issue they are experiencing? Are some functions not working properly, or is the entire form not accessible?

    In additon, there are a couple of possible reasons why your form may not work for some of your clients. It will be useful if there's a way to find out what's common to all of the 25% people who are not able to use your forms correctly. For example, are they using the same browser type and version? Did they access the form at a particular time? If so, when was it? Do they belong to the same geographic location?

    We shall await your response. Thank you for using JotForm!


  • Profile Image
    Answered on June 09, 2011 at 09:45 AM
    I think they're using a wide variety of different browsers, but all are here in Northeast Ohio. They all say that upon submission there are a series of alert screens - what those alerts are, I'm not sure. Sorry I don't have better answers; I guess what I was hoping is that you could look at our form and the website and make sure that we've done everything we can to ensure smooth delivery.Thanks, Matt
  • Profile Image
    Answered on June 09, 2011 at 04:49 PM

    Hello mariciamit,

    After looking into the source code of your form, what seems to trigger an alert is the facebook widget that you have installed in your webpage.

    The reason for this problem is that your website is using an HTTPS protocol but you have a script that that's being fetched from a site that's using an HTTP protocol.

    I saw two instances of this problem:

    1. <script src=""></script>
    2. <img src=""/>

    Both of these should be fetched from a secure socket layer on their respective websites.

    For your facebook script source problem, you have no problem with that and you can easily change the http:// to https://.

    As for your need_banner.jpg, it would be best if you could make another copy and place it in a folder on your website that can use SSL so for you to change it from http:// to https://.

    If you need further clarification with this issue, please let us know.