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

Question

Question

Different Favicon with New Designer

asked on September 29, 2022

I'd like to have my public facing forms have a different favicon than the default Laserfiche Forms one.  I know that I can just replace the file on the Forms Server, and I have done that.  But we have an added wrinkle that we have two different divisions with entirely different logos and colors, so I want the forms that I have built for one to include that logo and forms I have built for the other to have the alternate logo.

I can get this to work via Javascript, with code like this:

  //Update the favicon for the site.
  var link = document.querySelector("link[rel*='icon']") || document.createElement('link');
  link.type = 'image/x-icon';
  link.rel = 'shortcut icon';
  var baseSite = document.location.origin;
  link.href = baseSite + '/forms/img/favicon_alternate.ico';
  document.getElementsByTagName('head')[0].appendChild(link);

 

But in the case of the new designer, since I can't add that Javascript, I can't get it to work.

I was hoping there was an option in the theme settings on the designer to set the favicon, but I cannot find that.

I guess I can stick with the classic designer, but I do like how the new designer is easier to create forms that can resize to different browsers or for mobile with less effort than the classic designer.

Does anyone have any ideas or suggestions to make different favicons work for different forms using the new designer?

Thank you.

0 0

Answer

SELECTED ANSWER
replied on October 9, 2022

It is not supported to change the favicon for new designer, I will add it as a feature request. 

1 0
replied on October 11, 2022 Show version history

Thank you.

That and customization of the form title (instead of always saying “New Submission” - and I know that was suggested elsewhere on LFAnswers) will both go a long way.

0 0

Replies

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

Sign in to reply to this post.