- togafAsked on February 24, 2014 at 03:23 PM
1 out of 3 times when i close the browser (chrome, safari, firefox) i have issues loading the form on a page, it takes a long time. Users cant see the form and therefor leave the page without action, which is a real problem for us.
please help. I don't seem to have it with other forms.
i manage to record a video of the behavior
and have a inspector debug window catching the error details. see the attachment.Page URL:
- JotForm SupportTitusNAnswered on February 24, 2014 at 04:16 PM
Thank you for contacting us.
The issue might not be universal, I tested the page quite a few times, and my inspector did not return the same error. I know this does not help, so please try the following...
I would like to propose a solution to speed up loading time and remove those sporadic protocol errors:
1. Create a blank page on your site, for instance: http://www.archimatetraining.nl/application.html
2. Paste your form's source code on that page, remember to create a Doctype, head and body elements.
Place the form's source code inside the body tags. - If you like, We could generate the form page code for you.
3. Create an Iframe using that page you just created. Why an Iframe? It wil Isolate possible script conflicts:
<iframe src="//www.archimatetraining.nl/application.html"height="1000px" width="450px" scrolling="yes"></iframe>
Place this iframe where the form's Iframe was, and it should work as before - this will enable the form to load directly from your server - and remove possible network issues that are causing these errors.
The Default Values
I noticed you had some default values set for the first three fields using a prepopulation URL.
Before you get the source code, you can set the values as shown below:
Please let us know if this helps.
- joostbleijenbergAnswered on February 25, 2014 at 06:20 AMHi thanks,
About the default values. The main reason is that i want other fields to
appear depending on the page that is called. For instance language
depending but also the type of training.
How will this work with the approach you mentioned above?
- JotForm SupportTitusNAnswered on February 25, 2014 at 07:27 AM
The prepolpulation of those values can be done in various ways.
They can be easily configured using the value attribute. Your form's source code will make this even the more easier to apply.
Its the same attribute that is utilized with the default value setting in the form builder - so I would not worry about that too much.
The main objective of the workaround is to dramatically reduce the load time by hosting the form directly on your website - while maintaing the look, feel and functionality.
We would love to help towards that- why not create a test page so that we can advice before you put it live?
- joostbleijenbergAnswered on February 25, 2014 at 08:10 AMok i've tried it and it seems pretty fast now to load.
What is the issue with the access to your content. is it the CDN? or is it
maybe the fact that we have the http://form.jotform*eu*.com/ in stead of
- JotForm SupportTitusNAnswered on February 25, 2014 at 08:18 AM
Glad the test worked - I see you even sorted out the prepopulation of the first three fields. :-)
Yes - While our CDN is invaluable in delivering content - sometimes there are some issues with networks vs locations among other convoluted factors.
There are areas around the world, in my experience, with subnet proxies which lock out certain CDN content like scripts and CSS files -
The issue with the Iframe is not uncommon, depending on :
1. Your webserver responses to the remote content - and possible CDN issues
2. Possible script conflicts depending on the browser
I hope this helps. Let us know if you hit a bump.
- joostbleijenbergAnswered on February 25, 2014 at 08:20 AMHi Titus,
My only challenge now it so keep the fixed content in de html synchronised
with changes made in the formeditor, since these are made by different
Any thoughts ?
- JotForm SupportTitusNAnswered on February 25, 2014 at 08:27 AM
I'm afraid you would have to update the form's source code as it is hosted each time you make a change on the form editor.
You don't need to update the form's Iframe thogh
This workaround kind of takes automated updating away from you - sorry about that..
Perhaps a way for the editing team to collaborate and update the source each time they publish changes?