Microsoft has just released Internet Explorer 8.  Unfortunately, some of the pages on our website have some issues when viewed with IE8's default settings.  In particular, the styling that we've done on our main page's tab control is causing issues.  Users can fix these issues on the client side by selecting compatibility mode (the button to the right of the URL field shown below).

Of course, a client side fix is never a user friendly fix.  Thankfully there is a meta tag that can be added to your site to force IE8 to automatically go into compatibility mode.

Our page is built in Dot Net Nuke.  The appropriate way to apply this fix for DNN is to add the tag to the default.aspx file that is found in the root directory of your Dot Net Nuke website.  Any meta tag that is placed in here should be applied to all pages to your website.  Add the tag highlighted below in red at the top of the head section of the default.aspx file.

 <head id="Head" runat="server">
    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>

Note that the tag must be placed at the top of the head section.  Also, be aware that updates of your DNN framework will overwrite this change.

This is more of a short-term fix.  In the long run, we will want to determine exactly what is causing these issues and get the pages to display appropriately in the new IE8 engine. 

Thanks to Ty Seddon of CogniVista and Sebastian Leupold who contributed to this fix and Tim Warr, for posting about the meta tag for IE8.

Posted in: Dot Net Nuke
Share this page:

Comments

-->
# DotNetNuke Consultant
Thursday, November 05, 2009 10:34 PM
Wow, I didn't know there was a meta tag to force compatibility mode! That is great, that should help us out with some cross browser items. Although with new projects the only pain in our neck is IE 6.

Nice article

James - the DotNetNuke Expert and Drupal Consultant
-->
# giocare per vincere
Wednesday, April 21, 2010 11:14 PM
Thanks for the info! Is the back up/overwrite on framework update concern only a concern because it needs to be at the top of the meta tags, or are all meta tags, links, etc., placed in the default.aspx header overwritten on a framework update?...
# Matt Puskala
Thursday, April 22, 2010 5:08 AM
I believe it is completely overwritten.
-->
# FESTA COMPLEANNO ROMA
Thursday, July 01, 2010 4:30 AM
This is so cool..thanks so much for the info. Love it!S
-->
# Simone Moreali
Tuesday, October 18, 2011 8:37 AM
Try to use this one instead.



http://msdn.microsoft.com/en-us/library/cc288325(v=VS.85).aspx
-->
# Simone Moreali
Tuesday, October 18, 2011 8:38 AM
Try to use this one instead.



http://msdn.microsoft.com/en-us/library/cc288325(v=VS.85).aspx

Post Comment

Name (required)

Email (required)

Website

Enter the code shown above in the box below