The problems will relate to your OLD skin.  There are a lot changes in dnn 600 that can conflict with old skins, especially some of those that have been badly designed using workarounds in the past.

The issues will most likely relate to the use of z-index or lack of it in your old skin as a start - in your portal.css try adding 

.DnnModule {z-index:1;}

Or failing that - if your skin has z-index settings already - u will need to look at making sure its settings are not in conflict with them.

Start but looking at the content div  and setting z-index: 0; 

Basically, z-index is used to determine what layers elements are rendered on - if you have a div that is higher layered than a dnn element then that layer will get precendence.

Westa

I'm in the same situation as webqa here.

I've installed a brand new download of DNN 6.0 in a brand new environment (new database, new website even a new folder). I supose webqa (and a LOT of developers) is in the same situation and I think this is not a RTFM situation. I love the new skin and the new integration with the cloud, this is a revolution in DNN and I supose everyone agree.

But the problem is that I cannot see where I can create a new module from scratch and we, as developers, need that feature as the air we breathe (really, we are talking about MONEY here).

I have another framework question, but I will put it on a new thread to not pollute this one.

Kind regards