Hi all,

I have a layout issue where content in a few of my containers shows up 10-20px higher than I want.  So far, it looks good in IE8 and Firefox (still need to check lower versions of IE and other browsers). 

How do I add a conditional stylesheet for IE7 only in a DNN skin.  I found info on the STYLE skin object, but it appears to only work for IE6 and lower (unless there have been updates). 

Does anyone have any ideas?

Thanks,

John

All,

I was able to fix the issue after better understanding how the skin object worked.  For those of you that are interested, I just changed the line in the STYLE skin object declaration on my skin to reflect all browsers less than IE 8 instead of less than IE7.

So my declaration looks like this after changing the condition from "LT IE 7" to "LT IE8".

<dnn:STYLES runat="server" id="StylesIE6"  Name="IE6Minus" StyleSheet="ie6skin.css" Condition="LT IE 8" UseSkinPath="true" />

I would also suggest fixing the stylesheet name, ID and NAME values to reflect the change, but I didn't here since I am still just testing.

Finally, it looks like you can make this object specific to any version of IE by giving it a condition with out the LT (for example if you want it to be IE7 only, the condition would be Condition="IE 7") since this skin object simply builds out the necessary code for the header section of the page.

Hope this helps,

John

In which file you have changed.

My problem is my web application looking good in mozila firefox but when i open in internet explorer 7,8
 it's design changed and some textbox and button go out of the screen

 if you have solution  please let me know

First, make sure that your skin is set for XHTML compliance mode.  Check this tutorial: Browser Quirks, Standard Compliance modes and Doc Types

In current versions of DotNetNuke, there is a fallback Doctype that can be specified on the Host Settings page.  You should set that to XHTML but not rely on it.  Use a Doctype with your skin.

You will find that cross-browser issues are minimized this way.

I usually work in Firefox, so get the skin working there.  Then use the developer tools in IE to discover what CSS changes are needed.  In many cases, both IE and FF will work with the same CSS.  Sometimes IE is a little pickier than FF, so you have to make changes and test in both browsers.

Finally, look at the source for the Minimal Extropy skins to see how to use browser-specific CSS files to make the little corrections that you just can't make any other way.  If you have more than one or two styles that need changing this way, you're probably overlooking something.

I need help. I cannot figure out for the life of me what is going on with my skin that is causing it to not work in IE. It displays correctly in every other browser I have tested (FireFox, Safari, & Chrome). The problem in IE is the alignment is off, and it looks like all the padding I have set is getting stripped out somehow. I am new to DNN. My client requested that we use DNN to create this website since they use DNN for all of their other sites too, so can someone take a look at my site and give me any insight into why it might not be displaying properly? The website is http://www.geaugabizforum.com.

The one thing I have learned here is that I should make sure the skin is set for XHTML compliance mode. I realized that my skin is set to <!-- DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" --> so, I definitely need to change this. Do you think this will rid me of my alignment issues? I have combed the page with IE developer tool and I don't see anything that would be causing the alignment (floats) or padding to be off. Please help! I have to present this website to an audience in 2 days and I'm really going crazy to figure this out. Any help that can be given is much appreciated. Thank you.

For clarification, I'm referring to IE 8, IE 9, and IE 8 compatibility mode. Most of the info on DNN creative seems to address older versions of IE - so far I haven't come across anything addressing issues in these versions of Internet Explorer.

Also, I subscribed to DNN Creative to try to find the solution to the problem, and though I haven't found an answer on my own yet and am hopeful the forum will help bring an answer, I must say, Lee, you've done an excellent job on the video tutorials! Very thorough and informative!

Yes, getting your skin into XHTML Compliance Mode will make a difference. At first, though, you may find that switching modes may cause you to go back and have to fix other browsers.

IE is historically the hardest browser to skin, and cross-browser issues show up in IE more than other browsers.

If you look at the Minimal Extropy skin, you will see how you can use conditionally applied "correction" css files for various flavors of IE.

Thank you, Joseph. I will take a look at that and see if it helps. Do you see anything else that might be awry? I ran debugging and am getting two error messages.
1) Object doesn't support this property or method -- found in StandardMenu.js, line 19, character 5 which is -- $("#dnnMenu .topLevel > li.haschild").hoverIntent(config);
2) Object doesn't support this property or method -- found in jquery.min.js?1.6.1, line 16 character 15120 which is indicating the bracket after the word finally -- finally{b=[e,f],c=0}}return this}

I'm assuming this js code came in the DNN install.

Which version of DotNetNuke are you using?

Which menu is your skin using?

Where are you getting those errors?

DotNetNuke version 6.

I'll have to ask my developer in the morning what menu he is using. I'm afraid I don't know offhand.

While viewing my site in IE8, under Tools > Developer Tools. Under the Scripts tag, click Start Debugging.

Rachel,

Your skin seems to be using the DDR Menu. That's good. I can tell that from looking at your page's source.

With the IE9 development tools, your page looks good in any "standards" mode, so getting the DOCTYPE set should be a major improvement, if not the whole answer. (With the IE9 developer tools, you can switch to various browser modes.)

The javascript/jquery errors are red herrings as far as this goes. They are related to the menu operation, and it appears to be working just fine.