I experienced some weird problems with CSS not being picked up by DNN (from x.3.4 up)
There have been some posts about this and I think I found the problem (a least mine).
I had this only during quick experiments and thought I might be doing something wrong.
The problem is that sometimes one of the links to a  CSS files in the skin is not rendered.
I mean the actual link, in source of the output page, to the stylesheet is not there.
The problem occurs if you create a skin without a CSS file with the skinname, apply it and afterwards add a stylesheet (skinname.css). DNN somehow doesn't see the new CSS file and doesn't include a link to it..
Even "parse skin package" does not help.
There are two workarounds for his:
1. Restart the server.....
2. Login as host > host settings > Advanced settings > Other Settings > Clear cache

An example:

Create a skin pack containing: skin.css & myskin.ascx
Apply the skin to a page.
Now add myskin.css to the skin folder.
DNN will not link tothis file unless you clear the cache (I'm sure it did in previous versions)

---

Everything you should know is on these page:

http://www.dotnetnuke.com/About/DotNetNukeOnlineHelp/tabid/787/TID/1323/cid/-1/Default.aspx

and

http://www.dotnetnuke.com/About/DotNetNukeOnlineHelp/tabid/787/TID/1185/cid/-1/Default.aspx

Or you could download the documentation about skinning from the download page

---

Timo, I'm finding some challenges when working on skins as well - it's not you I don't think, and I'm finding it more obvious when working and updating frequently - it happens so much now that I have to use my dev machine - which is IE6, then I have to have IE7 which is my graphics machine and then FireFox which seems to be the worst lately - It hangs on the CSS for ages, and it's very very frustating to say the least.

I think there is the clear cache option from the text html editor - which shows up sometimes? or all the time? I'm not sure but having said it - I might look out for it and give it a try.

Nina Meiers

---