File folder capitalization problem with WebHelp skin

[adallas]

Our runtime logs are showing errors. The WebHelp is looking for "<help_dir>\Data\SkinPrimary\<image>" when what Flare output was "Data\Skinprimary\<image>".

Our .fltar file says "Skin="/Project/Skins/Primary.flskn" so the output generator seems to be mashing up the skin name with 'Skin'...and getting it wrong. I can "fix" it by renaming the "Skinprimary" directory to "SkinPrimary" after every build, but I'd rather not. I was surprised that a search for SkinPrimary across all forums here found nothing.

Any suggestions?

/alastair/

[i-tietz]

I don't think Flare itself is case-sensitive, but maybe your system is?

[lacastle]

I just looked at my output files to see if what you're seeing is common.
The name of my skin is DocLib. when I go to my output file, i find a Skin folder that has all the possible accordion htmls and a folder for the images in the skins, BUT these are not the images i use in my skin. these are images added by flare (like the searching animated gif, for example).
when i got to the Data folder, there is a folder called SkinDocLib (Skin+the name of my skin). that is where my used/custom images are stored.

is there a custom image you mention in your skin properties that for some reason that the link is broken to? i have my custom images saved in my project (not in output) as Content/Resources/Images.

and now that i read your question again, maybe it is just a capitalization issue with your folders/server at your company. so my above commentary probably didn't help much.
do you have other issues with capitalization in your folders?

[adallas]

Thanks for the replies, Inge and Laura. We are just using Flare's vanilla skin. As you noted, Laura, in the Data folder is another named Skin+SkinName, so in our case it's SkinPrimary. The folder name is actually Skinprimary on the disk, however, so we get an error, per image, logged on our server:

Code: Select all

<path>/Data/SkinPrimary/SearchAccordionBackground.jpg
Requesting: <path>/Data/SkinPrimary/SearchAccordionBackground.jpg

<path>/Data/SkinPrimary/IndexAccordionBackground.jpg
Requesting: <path>/Data/SkinPrimary/IndexAccordionBackground.jpg

I'm pushing back on our server administrator--I don't see why it matters on a Windows host where file names are not case-sensitive, but I wanted to check the Flare community. I suspect that if I change the name from 'Primary' to 'ourskin' it will output Skinourskin for the folder and the images will look for /Data/Skinourskin, but I haven't tried it yet.

[i-tietz]

There's a checkbox called Use lowercase filenames in the Target, tab Advanced. Maybe you should check that one and see whether that helps?

[LTinker68]

There's a checkbox called Use lowercase filenames in the Target, tab Advanced. Maybe you should check that one and see whether that helps?

Last I heard, that makes the topics lowercase, but leaves some of the project-specific files with mixed-case. You could try it, though, and see if that was changed in a later release.

I'm pushing back on our server administrator--I don't see why it matters on a Windows host where file names are not case-sensitive, but I wanted to check the Flare community.

To my knowledge, Windows has never cared about case sensitivity. Regarding your skin, did you double-check that you didn't condition out the skin file itself so it won't be included in the output? That capability (applying conditions to Project files) was added in v7, I think. Also, there is an option in the target to generate all skins (if checked) or to generate only the skin specified in the target. Double-check that you have that option enabled. If you renamed the skin, it's possible the target didn't pick up the name change and is still expecting the old skin name. If the generate all skins was enabled, then it probably wasn't a problem, but if it's not enabled, then it's looking for a skin that wasn't generated.

[i-tietz]

Not exactly case-sensitive, no, but different names, yes:
I upgraded to Windows 7 recently and was very surprised about the handling of some folder names.
Example:
I insisted on installing software into a folder called c:\Programme instead of the suggested c:\Program Files. Since then I have two folders called Programme ...
Why's that? There's one folder that is really called Programme (which contains that software I installed) and one folder that is actually called Program Files, but in the folder tree in Explorer it's called Programme just like in the address line at the top of Explorer, too. But if I click into the address line to get the whole path as a string, it turns into Program Files ...
=>
Programme is the virtual name, not the real name ... maybe Flare does something like that, too? Or maybe Flare uses a Windows-7-mechanism that does that?

[i-tietz]

Another idea: Rename the skin.
This behaviour could also have "historical reasons" - this bit of developer speech translates to: "We did something ages ago and we didn't check if it has to be adapted to the new mechanisms we integrated recently." (At least that's what our developers say.)
Since "Primary" is the default name of the default skin for ages ...