Question

Issue with using Custom HTML Field in Forms 10.2 for Google Translate

Forms Version 10

Updated August 24, 2017

asked on February 8, 2017

Hello,

Has anyone seen any issue with using the Custom HTML field in 10.2 Forms? We have the below input in the HTML tab:

<div id="google_translate_element"></div><script type="text/javascript">
function googleTranslateElementInit() {
  new google.translate.TranslateElement({pageLanguage: 'en', layout: google.translate.TranslateElement.InlineLayout.SIMPLE}, 'google_translate_element');
}
</script><script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>

We noticed though that when we try and submit a form that has this in the Custom HTML field, the form won't save to Laserfiche and gets suspended. The error that correlates with this in event viewer is as follows:

"Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: The PDF generator was unable to contact the Laserfiche Forms server. Please ensure your SSL settings are correct. [LFF4112-PdfNetworkError]"

If we remove the Google Translate field, the form saves with no issue.

Any idea as to what could cause this would be helpful, thanks!

2 0

Replies

replied on February 9, 2017

Hi Charles,

I tried adding customHTML field as your input, and save to repository worked in 10.2.0.789.

Can you check if your Forms server was able to access translate.google.com?

0 0

replied on February 10, 2017

Hello,

If I use Google Chrome to browse to translate.google.com, I get a :

Your connection is not private

Attackers might be trying to steal your information from translate.google.com (for example, passwords, messages, or credit cards).

NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM

If I use Internet explorer though, I am able to access translate.google.com

Thanks!

0 0

replied on February 12, 2017

Since it works for me I cannot tell if it's environment issue or something else. Maybe you could open a support case on the issue.

Still there is a workaround: you could copy the form, remove the customHTML field in the new form and use the new form in Save to Repository service task.

0 0

replied on April 26, 2017

Hello,

As a heads up, we were able to confirm that removing the google translate field resolved the issue. I had heard that the most recent forms update:

https://support.laserfiche.com/kb/1013834/list-of-changes-for-laserfiche-forms-10-2-update-1-

was supposed to resolved this. If not, what does laserfiche advise to do in order to get google translate to work in forms 10.2?

Thanks!

0 0

replied on April 26, 2017 • Show version history

Hi Charles,

There are several custom script bugs in 10.2 first release but none of them is related with your case, so the 10.2 update 1 fix won't affect your case either.

I have another workaround here: since the translate function is not supposed to work on printed form, you could skip connecting to google translate when printing form, with custom HTML field like this:

<div id="google_translate_element"></div>
<script type="text/javascript">
if (!window.isPrintMode){
function googleTranslateElementInit() {
  new google.translate.TranslateElement({pageLanguage: 'en', layout: google.translate.TranslateElement.InlineLayout.SIMPLE}, 'google_translate_element');
}
$.getScript("//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit");
}
</script>

This would make save to repository work even when I input invalid URL in it so it should work for you.

1 0

replied on August 24, 2017

We recently came across similar issues. It appears to be either SSL related or authentication related to the site you try to connect to. If we removed our Custom HTML which had iframe controls then it would save properly. We get the error even if use a URL on the local server and it didn't matter if it was SSL or not, but if we used google.com it worked for some reason.

As a workaround we ended up creating a PDF version of the form to save it to the repository without the custom HTML element until this works better.

Our VAR is working with support to determine what the cause is. We're running 10.2.1.205 currently.

0 0

You are not allowed to follow up in this post.

Question

Question

Issue with using Custom HTML Field in Forms 10.2 for Google Translate

Replies

Sign in to reply to this post.