In the modern designer in Forms version 11.0.2212.30987 there seems to be a bug when entering an iframe in the Custom HTML field. I am able to add the field and enter the code to embed the iframe and then save it, but when I go to edit the field again and switch to code view, the code is gone. If I refresh the page and edit the field the code is back. I have tried this using a normal link and the issue does not occur.
Question
Question
Modern Designer Losing Code in Custom HTML Field When Entering iframe Bug
Answer
Hi, This bug has been fixed on Forms 11 Update 4.
You can see other changes from:
List of Changes for Laserfiche Forms 11 Update 4 - Knowledge Base
Get Forms 11 Update 4 from Laserfiche 11 package:
Software versions and fixes included in the Laserfiche 11 Download Package - Knowledge Base
Replies
I feel like this is a bug too.
I can get it to save and work if I save the form while the "code view" is still enabled on the custom HTML element. But if I switch to the regular view or select the custom HTML element again after saving (because it's now on the regular view as the default) the iframe disappears.
It's annoying to need it - but until they get the bug fixed - here's a workaround. You can set the HTMLContent of the custom HTML element via Javascript on the form.
Example:
LFForm.changeFieldSettings({fieldId: 3},{HTMLContent: '<iframe src="https://www.google.com/" title="Google Search" width="750px" height="400px"></iframe>'});
Then you can just leave the Custom HTML element on the designer showing the default text and not worry about it.
Note that the example I included with google.com did show the iFrame but with a message about the page refusing to connect. This is because Google, as with most major websites, doesn't allow access via an iFrame. But I was able to get this to work with a link to another Form process in our environment, so I know it is working and I left it listing Google even though that doesn't work, since I didn't want to include an internal URL.
This has been identified as a bug. Thank you for reporting it. The bug reference ID is 422152.
I have verified it in both self hosted and cloud layout designers.