This is the second site that I have had this happen to me on. If you login, the login menu at the top (where you can add pages/modules etc) is stretched extremely wide. My skin is literally a single content pane div with no css. Do you have any ideas on how to fix this? I have attached some files to illustrate my problem and my skin.

I've had this happen to a third site now. I literally put nothing in the skin but a contentpane and the tag to the skin.vb file. Has anyone else had this problem, and if so, does anyone have a fix.

I assume that you are referring to the control panel? If so, its size and placement are controlled by an element in the skin. It's the div with id="ControlPanel"

If there is no such div, I assume that DotNetNuke places the control panel in the ContentPane. If that is full-width, so will be the control panel.

Are you suggesting I add a div id="ControlPanel" with some sort of width? If so, I tried that, it didn't fix anything. I then set overflow to scrolling and it kept the control panel in a width, but none of the buttons work in it still.

Yes, a "simplest possible" skin might look like this:

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

< div runat="server" id="ControlPanel" >< /div>
< div id="ContentPane" class="ContentPane" runat="server">< />

(Don't forget to remove the extraneous spaces I placed in the tags to make this postable.)

Adding that does not solve my problem.

What does the CSS,file look like?

Ok, I finally found the problem. You made a light bulb go off in my head when you asked about the css file. I had removed the link to the css file so I thought it was irrelevant. However, even though there was no < link href="my.css" ... > in my file, it still was effecting the file. I realized this because my body bg color was still showing. I finally found the culprit. I had a css class called
.footer{
width: 972px;
text-align: left;
}
For some reason, having that class screwed up the control panel. I changed it to footerText and the problem disappears. The reason I had this problem in two other sites is because that is a common naming convention for me. Thanks for the help.

I'm glad you found it.

This oldie but goodie is worth reviewing:  Troubleshooting DotNetNuke Skins

Since it was created, IE and Chrome now have built-in tools, too.

When in doubt, I will open up Firefox, and start deleting contents of various CSS files to identify where the problems are located.  Then I'll drill through the problem file to locate the offending class.


Happy New Year, too!

That's exactly what I had to do. I didn't realize that DNN automatically linked your css file for you. That's why I didn't think the css could have anything to do with it. When in doubt, start deleting things till you fix your problem!