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.


  • Profile Image

    Link to Secure Form works but shows "Only Secure Content is Displayed" and in some browsers will not display Security Seal.

    Asked by Janet  on October 28, 2014 at 03:19 PM

    We have an employment application form that we've created that is about to go live.  We pulled the link address (we will not be embedding the form but linking to the secure form on your site) from the Embed Form button which shows in the format of https://secure.jotform.us/form/formnumber so this is the link we are using.  Through testing, we've found that in some versions of IE (IE 11 for sure) it displays the Security Seal we added, but pops up a warning at the bottom stating that "Only secure content is displayed" with the option to show all content.  But, in Chrome and Firefox the Security Seal doesn't display but says javascript needs to be enabled.  This form is pulling very sensitive information (i.e. SSNs) so it needs to be secure.  The form is integrated with Dropbox so once an applicant submits, a copy is sent to our Dropbox where HR can securely retrieve it.  We are new at the whole Jotform thing and are wondering if we did something wrong or why we are running into this.  Any guidance?  I can give you the actual link, but we really don't want to deal with a whole bunch of possibly bogus job applications, so I'm hesitant.  Thanks.

    seal secure https SSL Only secure content
  • Profile Image

    Answered by Ben on October 28, 2014 at 04:33 PM

    Hi Janet,

    Please clone your jotform ( How to clone an existing form from your account? ) and then give us the link to the clone on the forum. Once we help you with this, you can just make the same changes on the original jotform (or clone it once again) and remove the one that you have left the link for on the forum.

    Our Secure links should not display such warnings, but we would be happy to take a look at what could be causing this issue.

    Best Regards,
    Ben

  • Profile Image

    Answered by Janet  on October 28, 2014 at 05:36 PM

    I've cloned the form and here is the link:  https://secure.jotform.us/form/43006431690144

    If you can figure out what we did or why it's acting non-secure, I'd appreciate it.

    Thanks,

    Janet

  • Profile Image

    Answered by Ben on October 28, 2014 at 06:00 PM

    Hi Janet.

    Thank you for posting the link.

    I see the issue and will contact our developers in regards to this.

    The issue is caused by the widget ScrollToTop. If you remove it from your jotform for now the error message should disappear for you.

    Once our developers correct this you would be notified through this thread so that you can add it back to the jotform once again.

    Best Regards,
    Ben

  • Profile Image

    Answered by Janet  on October 29, 2014 at 12:31 PM

    Thanks for your quick reply.  We removed the ScrollToTop widget from our actual form as it is not a truly necessary component and testing has verified that the security issues have disappeared.  Thanks for your help.  If the problem with the widget gets resolved and you post that here, we may consider adding it back to our form.  Thanks again!

  • Profile Image
    JotForm Support

    Answered by jonathan on October 29, 2014 at 02:34 PM

    Thank you for updating us on this.

    It is good to know that you have found a working option at this time. 

    In any case the discovered glitch on the widget had been found and was now assigned to our developer to be fix.

    They will update this thread when update status is available.

    Thanks.