Hi Stef,

As far as I know it still works the same, the admin pages (under Administration Menu) use the site default skin and pages can use specific skins. Note however that you may be thinking of PageLayout.aspx and PageSettings.aspx and they are in a sense admin pages but since they are specific to the page they must use the same skin as the page, especially PageLayout.aspx because a page may be using a skin with more than 3 content panes and if we use the site default skin there it will not have all the layout sections needed by the page.

All skins in mojoportal support from 1 to 3 columns with automatic layout, so having different skins with different numbers of columns sounds like you are working against the grain of the system. ie we don't make any skins that only support 1 column, we just hide the side columns if there is no content there.

Hope it helps,

Joe

Hi Stef,

I think it does not work correctly when you have this setting:

<add key="CombineCSS" value="false"/>

but if you set it to true it works correctly. It should be true on production sites to improve the page load speed, you are loading a lot of separate css files and they are not minified. For production it is best to enable both combining and minifying of CSS.

Hope it helps,

Joe

Hi Stef,

I was not able to replicate the problem of incorrect skin name with css handler, in my testing if I set specific skin on the home page (not site default) then when I go to pagelayout.aspx is shows the correct page specific skin name. 

I do agree it is a bug about the IE specific css and the favicon, I have fixed those this morning, they are fixed now in the source code repository so they will be fixed in the next release. I also fixed it so that if CombineCss is false it correctly resolves the individual css file urls and uses relative urls.

Best,

Joe