Afternoon folks...

Ok, I've now been handed a site design, fully html'd and css'd, by my boss.  Looks decent, and most of the content is 'containerized', so the main trick I've got is to import the existing layout into a DNN skin, then create the containers and plug in the modules I've already got built. 

This 'template' I've been given has Javascript and CSS files which I need to include into the site.

I've now removed the content containers from the site and set up content panes where they will go.  Added .js to the accepted files list under host settings so that those files will upload correctly. 

Now, the problem I'm running into is that when I upload the skin, things go south.

I think I have figured out WHAT the problem is, but am not sure how to deal with it.  It is my belief that the error which is being represented by

A critical error has occurred.
The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>).

Substituting: <link type="text/css" rel="stylesheet" media="" href="content/css/layout.css">
With: <link type="text/css" rel="stylesheet" media="" href="<%= SkinPath %>content/css/layout.css">

in the import report.   I've noticed it on the images as well, but they are showing up correctly... It's my belief that the <%= SkinPath %> occuring in the page header, where you are supposed to put links to any and all CSS files (and JS files) is whats causing the problem.  From some googling, you're not supposed to put <% into the page header, but DNN is the one doing this... As such, I'm not sure of how to solve this problem...

Any thoughts would be appreciated... I'm on a pretty tight deadline here and the longer I'm stalled by this problem in even loading the skin, the less time I can be working on content modules.

Thanks,
Brian

*nods* 

I see what you were saying... One issue that I noted was that the process of uploading the skin seemed to strip out the css includes that I was putting in. 

So, what you said only was 50% of the issue.  I also ended up using ResolveURL capability, having the six additional CSS files resolve into the body of the skin.  I didn't realize it at the time that I wasn't using skin.css at all... 

<link rel="stylesheet" href='<%= ResolveUrl("~/DesktopModules/path/path/path/layout.css") %>' type="text/css" />

Well, if by want, you mean, is there a reason I'm against it, then no... Or, if by want, you mean, why didn't I think of that *laughs* 

Seriously though, I'm not sure that @import, now that I'm thinking about it is a good big picture solution.  The reason for this is that I'm going to need to be able to use different CSS files, depending on what URL path I'm at, for various skins... Basically, we're going to have different CSS 'skins' for different parts of the site, all of which, hopefully, will eventually be using just a couple of actual skin files... As such, since a CSS is a text only file, and cannot contain any functional logic, simply importing all of the CSS files into a single skin.css wouldn't be a viable solution.

Brian