JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
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.
Squarespace iframe or widget field not fully loadingAsked by art_crate on June 29, 2016 at 04:48 PM
I recently had a user send me a screenshot of a broken survey. Please see attached image. Why would the form partially load, but not show the questions?
Is there anyway to embed the form on Squarespace so this doesn't happen?
Inside of this guide you can find how to add a form to Squarespace:
If the issue still persist, please provide us URL of your webpage.
Hope this will help. Let us know if you need further assistance.
That is the process I followed to insert jotform into squarespace. Can you think of any reason why the form would not load?
The only issue that I have noticed is the mixed content warnings, some images are served via HTTP on your HTTPS form.
It is advised to load all the form resources over SSL since depending on the mixed content type and browser settings, such content might be blocked by internet browsers.
I have all of the images hosted on Photobucket. I am not quite sure how to have them all the resources load over SSL. Can you advise on how I should host and connect the content?
The widgets were loading and images can be seen.
Here is the screencast video when I test.
Can you please confirm that you are still having the issue at this time.
If it is, perhaps you can test using a different browser also. See if that makes any difference.
The issue was sent to us by a user. I have been unable to replicate the error.
His setup below:
PC, Windows 10, Chrome browser
Thank you for the clarification and providing more details.
I also used the same setup mentioned by your user. But I could not reproduce the same errror.
It is highly possible the issue was occuring only for that specific user.
Were they able to consistently replicate the issue? If it is, can you suggest to them to try it also on different browser or computer if possible also.
Let us know if this issue persist on that user.
Thanks for the update Jonathan. I am assuming this was an outlier case. I will let you know if we can replicate the issue.
Thank you for all the help!