You are viewing limited content. For full access, please sign in.

Question

Question

Embedded LF Form Error "Protocols, domains, and ports must match"

asked on January 21, 2016 Show version history

We have some embedded forms that were working great with Forms 9. Some of them have a signature field. We have upgraded to Forms 10 and now the same forms are having a problem displaying the signature modal popup when you click the sign button.

Below are the console errors from IE 11 and Chrome 48:

Chrome:

IE:

Does anyone know if this is directly related to the upgrade to Forms 10 or something else?

2 0

Answer

SELECTED ANSWER
replied on April 28, 2016

This issue is addressed in Forms 10.1

Thank you.

0 0

Replies

replied on January 22, 2016

Have you tried the solution provided in this Answers post? 
https://answers.laserfiche.com/questions/87623/Iframe-no-longer-working-with-Forms-10

It looks like your Chrome console error is the same as the one in the post.  


If it still doesn't work, can you provide additional details regarding your setup?

 

Regards

0 0
replied on January 22, 2016 Show version history

According to that post the issue was resolved in Laserfiche 10 Update 1. That is what we are currently running. I did check the Forms.js file and it does include the same line of code mentioned in that post.

0 0
replied on January 22, 2016

The other weird part is that some users do not have the problem.

0 0
replied on January 22, 2016

Is this possible that some users have a cache of the old js file in their browser? Can they clear cache and try it again?

0 0
replied on January 24, 2016

Hi Blake, we want to check for those user that has this problem, whether the content loaded in their browser contain the related fix.  Can you open Chrome Developer Tools when load the embed form and go to Network tab and find the request start with "formlayout?=" and double click the name of the request so that Chrome will open the response in individual tab, search for keyword "catch(err)". If search can get result, then the content loaded in the browser contain the related fix.  You can refer to http://screencast.com/t/0YisexQoT for how to perform the check.

0 0
replied on January 26, 2016

I checked the browser of a user where it is having the problem and one that is not having the problem and both of the browsers contain the related fix when I do as you suggested to look at the code. We did not have this issue in Forms 9, only in Forms 10. Any ideas?

1 0
replied on January 26, 2016

Are you embed form by using embed code generated from Forms publish page or use iframe?

We are able to reproduce this issue when use iframe and when the height of iframe is very long and the form is very long and the signature field locate at the bottom of the form.

And here is the workaround you can try:

backup the forms.js file(C:\Program Files\Laserfiche\Laserfiche Forms\Forms\js\form) and modify the file by changing

if(LF.inIframe()&&!isMobileBrowser&&(window.innerHeight>Math.max($('html').height(),$('body').height())||window.innerHeight>window.screen.availHeight))

to

var canGetParent = false;try {var test = window.parent.document;canGetParent = true;}catch (e) {}if (canGetParent && LF.inIframe() && !isMobileBrowser && (window.innerHeight > Math.max($('html').height(), $('body').height()) || window.innerHeight > window.screen.availHeight))

You can search by "isMobileBrowser" to locate this piece of code.

 

Refresh the page in the browser and check whether the signature dialog can be opened, after apply this fix, the signature dialog will appear at the very top and you need to move the scrollbar up to see it.

1 0
replied on January 27, 2016

That was exactly our setup. We are using it in an iframe and not the embed code. We had to change the code to make the height larger.

After editing the Forms.js file with the work around code, it works as expected.

1 0
replied on May 26, 2016

This has been fixed in Forms 10.0 update 2, you can download the update from https://support.laserfiche.com/kb/kbarticle.aspx?articleid=1013773

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.