Hoping this has happened to some one before.

I am currently building a skin to work with DNN 6, It is a simple enough skin with a header, main section with 2 panes and a footer at the bottom.
The problem i am having is that when i post multiple times into the contentpane the main section that holds the content pane is expanding as the number of contentpanes increase. Eventually this leads to the contentpanes overlapping on to the footer and past. I have tried removing all my code and putting the skin into its simplest form, the header, main and footer with the contentpane in the main div. The problem is still ocuring.
Is there any reason for this or a way around it.

CSS:

#wrapper
{
width: 100%;
height: 100%;
margin: auto;
}
#header
{
width: 100%;
height: 140px;
background-color: #333;
}
#main
{
width: 760px;
height: 100%;
}
#footer
{
width: 100%;
height: 140px;
background-color: #333;
}


ASCX File:

< %@ Control language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Skins.Skin" %>

< div id="wrapper">
< div id="header">
< /div>
< div id="main">
< div id="contentpane" runat="server">< /div>
< /div>
< div id="footer">
< /div>
< /div>

It would help to see the skin file, too.

Oops, sorry ... it is there with some help ...

I made a simple skin using your code. It's attached.

It works just fine for me.

Hi nick,

If you are still having issues I had the same problem so I took the dark knight skin and edited that to look like my old table based dnn 5 skin and now I have a css skin that works great. I found there was several issues with dnn 6 and dnn 6.0.1 and these all varied depending on if it was a fresh install or an upgrade and which version you started with before upgrade. DNN 6 adds loads of code to the default and portal css files which made my skin stop working but without these bits of code the manage button and other things do not work. I use the dnn360 mega menu in my skins and that was suddenly throwing all sorts of problems into the works then I found it was hiding behind things because in default.css there is a section called dnnmodule if you set the z-index from 902 to 1 many things start to work and be in the correct places. Let me know if this does not work but this solved 90% of my issues.

Thanks
Paul

Thanks for the responses Joseph and Paul.

Found the problem eventually, it turns out I had entered the doctype incorrectly. I had entered:

<--![CDATA[http://www.w3.org/TR/xhtml1/DTD/xht...tional.dtd" target="_blank" rel="nofollow">http://www.w3.org/TR/xhtml1/DTD/xht...tional.dtd">]]-->

which makes it into a comment by removing the -- lines it solved most issues I had on the site, turning it into:

http://www.w3.org/TR/xhtml1/DTD/xht...tional.dtd" target="_blank" rel="nofollow">http://www.w3.org/TR/xhtml1/DTD/xht...tional.dtd">]]>

not sure why I had the -- lines maybe I had copied and pasted it from somewhere that had it wrong, or I just wrote it wrong.

Thanks for all the help

Paul,

That's a reasonable way to go.

The 6.0.1 version has (I think) all of the z-index issues fixed.

The "loads" of stuff added to portal.css is exclusively (I'm pretty sure) for the default site for the bicycle shop. You can clear it all out and not damage anything.

Nick,

Great!