Form not loading when linked from Squarespace button or text link

  • Profile Image
    Asked on April 10, 2019 at 04:50 PM


    I have been very impressed with JotForm and want to use it on my Product Photography site and step up to the bronze plan, but I'm having an issue with Squarespace integration.

    I embedded the form in our Squarespace site, but it does not load when it's linked from another page via a button or text link. It loads once the page is refreshed or when it's directly linked from an external source, but not when the page is first opened via link from our site's Product Photography page. 

    Here is a link to our Product page so you can see the issue. Click one of the "Get Started" buttons or the "reach out" text link. 

    Here is a direct link to page with the embedded form. 

    I embedded it using a Code Block and with the following code:


    Let me know if you have a solution to this or any suggestions, because I love the platform and want to use it, but this would prevent it from being worthwhile.


  • Profile Image
    Answered on April 10, 2019 at 06:57 PM

    I can see that the form does not load at first if the user is redirected using the button. However, the form loads as soon as I refresh the webpage.

    Could you please try to embed the form using the iFrame method?

    Guide: Getting-the-Form-iFrame-Code

    Please give it a try and let us know how it goes.

  • Profile Image
    Answered on April 10, 2019 at 10:26 PM

    Good to know that you were able to find a workaround. 

    I think what you're looking for is achievable with the full source code of the form. You can get the source code, modify it to your preference like adding PHP's cURL functions etc. If you want to try it, please see the guide below.

    Guide: How-to-get-the-Full-Source-Code-of-your-Form

    Please note that this method requires coding so you can hire a developer if you want to use this method.

  • Profile Image
    Answered on April 11, 2019 at 05:58 PM

    Thank you! I think I'll stick with the workaround for now, but it's good to know this is an option if we need Ajax features in the future.

    I appreciate your help. Have a good one!