"Missing linked stylesheet" error but its there

[oceanclub]

I'm updating a Global project and want to make sure it is completely solid before I roll it out.

There is one issue when I build a HTML5 project which imports from this global; I get the error:

Code: Select all

   <LogEntry Message="Missing linked stylesheet /Content/Resources/Stylesheets/StylesForHomePage.css
" LineIndex="-1" CharInd

However:

• The given file - imported from Global - is confirmed to be in that location
• The styles in it - only used in the Home.page of the project - seem to be applied correctly to that page - the Home page looks as expected

As an experiment, I then changed the link in the Home.htm file to point to a non-existent file (I just appended RENAME to the end of the stylesheet:

Code: Select all

     <link href="Resources/Stylesheets/StylesForHomePageRENAME.css" rel="stylesheet" type="text/css" />

Running the target I get the following:

Code: Select all

    <LogEntry Message="Missing linked stylesheet /Content/Resources/Stylesheets/StylesForHomePageRENAME.css
" LineIndex="-1" CharIndex="-1" Subsystem="CSS" Target="Template 2" ErrorID="10010" />
        <LogEntry File="../../../Content/Resources/Fenergo/Content/Home.htm" Message="Missing linked source file: C:\Flare\FlareProductOffering\Content\Resources\Stylesheets\StylesForHomePageRENAME.css
" LineIndex="-1" CharIndex="-1" Subsystem="Compiler" Target="Template 2" ErrorID="10001" />
        <LogEntry File="../../../Content/Home.htm" Message="Missing linked source file: C:\Flare\FlareProductOffering\Content\Resources\Stylesheets\StylesForHomePageRENAME.css
" LineIndex="-1" CharIndex="-1" Subsystem="Compiler" Target="Template 2" ErrorID="10001" />

This is interesting as it confirms the error is not being produced by any other file other than home.htm - otherwise I would still see an error related to StylesForHomePage.css. Now I have three errors because the file is genuinely missing. But it looks like Flare is producing an error even when the file is there?

P.

[ChoccieMuffin]

The way it seems to work is, when you build your target, it tries to build, notices the stylesheet isn't there, runs all the imports then tries to build it again. So you get the error because you don't have a copy of the stylesheet already present in your project structure.

I agree, it's a pain, but for our projects (where we only keep stuff in source control that is unique to a project, not imported bits from our Globals project that we import) we get loads of these warnings and just have to ignore them.

You could always put in a feature request (see my footer) to change the way the warnings are logged, so that a warning isn't even mentioned if a subsequent action, such as running an import file to import the stylesheet, means the warning becomes obsolete.

[oceanclub]

The way it seems to work is, when you build your target, it tries to build, notices the stylesheet isn't there, runs all the imports then tries to build it again. So you get the error because you don't have a copy of the stylesheet already present in your project structure.

I agree, it's a pain, but for our projects (where we only keep stuff in source control that is unique to a project, not imported bits from our Globals project that we import) we get loads of these warnings and just have to ignore them.

You could always put in a feature request (see my footer) to change the way the warnings are logged, so that a warning isn't even mentioned if a subsequent action, such as running an import file to import the stylesheet, means the warning becomes obsolete.

Aha - yes, it is a pain as I imagine like me you might spend a few hours bugfixing. :/ I'll put a request in.

P.