Installing Optional Fonts - Advanced Installer Community
rodkort
Posts: 3
Joined: Tue Jul 28, 2015 3:51 pm

Installing Optional Fonts

Hi,

I'm creating an installation that has optional features, and depending what is selected the appropriate font is installed.

Whenever I add new fonts they are always grouped under existing fonts in the MainFeature, and I can't seperate them, the 'Move to new component' option id disabled.

What am I doing wrong? And is it possible to add fonts in 'Files and Folders', and to have them as individual components?

Thank you

Simon
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Installing Optional Fonts

Hello Simon and welcome to our forums,

I've tested this and replicated the behavior. This seems to be an Advanced Installer issue, thank you for bringing it to our attention. A fix will be available in a future version of Advanced Installer. We'll notify you as soon as the fix will be out.

Until then, as a workaround, you can create in "Files and Folders" page, under the fonts containing folder, a subfolder for each of your font file. In this way AI will automatically create a separate component for each of your font file. Then, to install the font file in the parent folder you should enable the "Install folder content into the parent folder" option for all the above subfolders.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
rodkort
Posts: 3
Joined: Tue Jul 28, 2015 3:51 pm

Re: Installing Optional Fonts

Hi Daniel,

Thanks for replying and showing me a work around. Look forward to the fix :D

Cheers

Simon
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Installing Optional Fonts

You're welcome Simon. We'll notify you when a fix will be out.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Installing Optional Fonts

Hello Simon,

Our development team finished investigating your reported ticket. It seems the "Move to new component" option is disabled for font files because of an old Windows Installer bug. When a resource is moved into a new component the resource it is set as the component key resource, but when a font file is set as a key resource of a component this could trigger an old Windows Installer issue. Unfortunately, our guys don't remember exactly what the bug was about, but they are sure this is the reason why we don't allow you to move a font file into a new component. So, long story short this is a safety measure to prevent an old Windows Installer issue.

So, to achieve what you want you should always use the workaround I previously mentioned.

Thank you for your understanding.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”