Not too sure by what you mean with the top menu. If it is the blue bar with the web, site and search then load the ascx file for the skin into frontpage,dreamweaver or visual studio and then edit the html - it will most probably sit between a <td></td> tag - delete the whole tag and its gone.

Care should be taken with front page when you edit a ascx page with front page it can sneek a html and body tag in ie try to turn it into a aspx.

Not too sure of what your site does - my swedish is non existant.

The best way to learn skinning is to pick up a skin that has the html file rather then the ascx - check the skinning documentation ( available on the dotnetnuke site) for the skin tags that are available ie [currentdate] [usrer] etc - if you work on the html rather then the ascx it is much easier and when you install the skin dnn will generate the ascx file for you.

The skin you appear to be using is dnn blue -comes with dnn. in the Portals\_default\Skins\DNN-Blue directly you will find the htm for this skin.  Copy the htm,css,xml and the gtraphics to another directory  and work on them - then when you change the skins zip all to a zip file and install it using the admin/host menu.

I'm also a bit unsure of what's going on with all that, but you might find it easier to avoid the skins upload page altogether when developing a skin. It's fine for uploading and applying a fully tested skin package, but it only complicates things when you're trying to build a new skin.

You'll know most of this already, but I'm going to touch briefly on a basic skin editing prodecure because it would have helped me at the time.

• Examine the skins and containers folder structure on a fresh install so that you know where things go.
• Take note of how Host skins reside in the _default folder, but portal skins reside in the respective portal folders.
• The DNN default skins are host skins.
• Then also learn the difference between the files in the skin package so that you know why you're going to edit the ascx files rather than the HTML/XML files
• DNN combines HTML and XML files and builds ASCX files from them.
• ASCX files are the actual skins and any edits to them are shown in real time on the site
• You can create folders for skins and containers following the structure of the default skins
• Upload skin and container files to the folders
• Go to the Admin Site Settings page and apply a portal skin and portal container
• You can also apply an Admin skin and Admin container (answering one of your questions)
• Use a wysiwyg editor (Frontpage, ExpressionWeb, Dreamweaver etc) to view and edit the skin's ASCX files directly on the server.
• View the results in a browser.
• You can undo changes immediately in your editor so long as you keep the file open - this should help you with those crashing problems.

If you have already learned the difference between HTML/XML and ASCX skin files then you may decide you want to edit the HTML/XML files instead of the ASCX. The main reason for doing this is if you are creating a skin for sale, as people like to have those files in the package. If you do edit the HTML and XML files live on the server, then you must take the extra step of parsing the skin (there's a button on the skins page) before you will see the results. This creates new ASCX files.

If you want to save the skin offline for distribution, just ensure that you place the skin and container files in the exact same structure as they are in a working skin package.

Also, check out this cool helper app: http://www.codeproject.com/KB/dotnet/SkinCreatorForDotNetNuke.aspx

Rob