- transpayAsked on October 01, 2015 at 02:22 PM
After I exported my form the visual multi-select widget field on page 2 (displayed if you select "B2B Sender Services" for the first question) disappears completely.
How the field looks on Jotform:
How it looks when I export it to my local drive:
Come on Jotform, what's going on?!
- BenAnswered on October 01, 2015 at 04:19 PM
Can you please upload the exported file somewhere - like pastebin.com so that we can see the exported file and the code within it to be able to see what might be the issue.
Per the screenshot, it seems as if the widget was not able to contact our servers to get the required data.
- transpayAnswered on October 01, 2015 at 05:44 PM
Here's a pastebin of the HTML: http://pastebin.com/WjqVsThi#
- JotForm SupportChriistianAnswered on October 01, 2015 at 11:55 PM
I have downloaded your exported form but I couldn't replicate the issue when I have ran it via my localhost server.
However, when I tested running the HTML file directly into the browser, I was able to replicate the issue.
As my colleague, Ben has stated, the widget may not have contacted our server to get the required data.
Do let us know if you need further assistance.
- transpayAnswered on October 02, 2015 at 12:36 PM
I'm not sure I understand what you're saying...do you mean to say that if I was to test it on actual live website that it would actually show?
- JotForm SupportWelvinAnswered on October 02, 2015 at 02:02 PM
Yes, that is because the HTTP or HTTPS protocol is removed in the widget URL. If you will inspect it, you will only see //widgets.jotform.io/multiSelect. For this to work, you will need to make it live instead of viewing it locally.
I hope that helps.
- transpayAnswered on October 02, 2015 at 02:40 PM
Thanks, the problem actually can be resolved by adding https: to the URL //widgets.jotform.io/multiSelect. Perhaps you can let your development team know? Thanks for your help.
- BenAnswered on October 02, 2015 at 02:59 PM
Actually the // (no protocol) is placed like that intentionally.
The reason for this is to allow the resources to be loaded over the same protocol - if you call the form over HTTP, you will have the widgets and other resources loaded over HTTP, the same goes for HTTPS.
The forms are intended to be used online, so the file protocol should not be there. Since you want to use your forms saved on your PC, my suggestion is to open the file in any file editor that you have and search for "// and have that replaced with "https:// instead (quote on the start is intentional).
That way it will work properly for you and for everyone else.
- transpayAnswered on October 02, 2015 at 03:00 PM
oh i see, alright i will remove it and test it after i push it live. Can you possibly help me with the style problem?
- JotForm SupportWelvinAnswered on October 02, 2015 at 04:25 PM
Your problem about the style has been moved here: http://www.jotform.com/answers/675537.