I've run across a problem when using SkinName.css and different skins for Portal and Edit skins in DNN 5.00.01. Basically, it goes like this:
In Admin Settings-> Appearance, Portal Skin is set to SkinA and Edit Skin is set to SkinB. SkinA and SkinB have SkinA.css and SkinB.css respectively. When on any page, the page renders with SkinA and has the link to SkinA.css in the header correctly. But, if you go to Page Settings, the page renders with SkinB as it should, but SkinB.css is not linked in the header, it still links to SkinA.css in the header. So in edit mode, SkinB is rendered incorrectly with SkinA.css and no link to SkinB.css. I've tried this with the skins having no links defined to the style sheets and letting DNN handle the skinName.css associations, and I've tried this with the links manually entered in the header in the html file (which really doesn't matter since the header is removed in the ascx file automatically by DNN anyway).
I had problems previously with the skinName.css and cache, but I've done the Host Settings-> Clear Cache, gone to the cache directory in the portal and manually deleted all files, and cleared my temporary internet files and cache, exited browser and closed everything down, etc. including reparsing the skins and this problem is persistent. I'm thinking this is a bug, but not sure if I'm doing something wrong somewhere and just overlooked it. Anyone have any ideas?
EDIT: note this does not happen if the Page Settings -> Advanced Settings -> Page Skin is set to <use portal default>. It only happens if the the Page Skin is set to a specific skin, in this example SkinA.