Susan,

Skins for DNN4 will work in DNN5 as well, the main difference is in the way the skin is packaged and uploaded. However seeing as version 5 is an upgrade of the framework there are some extra things that can be taken advantage of with regards to skins. An example of this is the menu provider (your skin is using the solpartmenu which isn't actively supported anymore) which can now be rendered as a list of links, making it much easier to work with and more importantly search engine friendly.

At the very basic, skins are a collection of atleast 2 files a skinname.ascx file which contains the HTML code and skin objects, and a skinname.css file with all of the style code. There can also be a skinname.doctype file which sets the doctype for the skin, and it's generally considered good practice to have this set to a XHTML doctype because this tends to sort a lot of minor issues. Ontop of this there can also be a skin.css file which contains shared CSS between multiple skins in a skin pack. All of these are located in either the Portals/_default/Skins/ directory (if it was loaded through the host extensions) or the Portals/"portal number"/Skins directory (If it was loaded through the Admin extensions).

If you need to make changes to the CSS in the skin I'd recommend using the Firebug plugin for Firefox (www.getfirebug.com) to examine the page code and make changes in your browser, and then update the necessary CSS or .ascx files in the skins directory. Remember to make a copy of anything your making changes to so you can revert back if you make any mistakes.

Alternatively you can also add CSS to the Stylesheet Editor in the Admin > Site Settings page which updates the portal.css file, and because this loads last the CSS has precedence.

The first thing I'd recommend doing though is adding a skinname.doctype file to set the Doctype to XHTML. It might be that this will sort the problems for you (http://www.dotnetnuke.com/Community/W...).

Hope this helps,

Rick.