Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Single-page IE Compatibility ModeSingle-page IE Compatibility Mode
Previous
 
Next
New Post
2/16/2011 2:41 PM
 
I'm working on a DNN Pro site (5.5.1) but I have a feeling this is common to both PE and CE - Simply, I need to make one page force IE compatibility to version 7 to make a module behave properly. The method I usually use for this is to use the following meta tag:

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" >

I can then verify the mode by putting this in the address bar once the page has loaded:
document.documentMode);

Now, ideally since this is only needed on one page, I'd prefer to do it in the "Page Header Tags" section in Page Settings > Advanced. Unfortunately, when I put in the meta in there, it still says it's using the current browser version (8 in my case). Now, if go old-school and just manually add it to the top of the head section in the default.aspx file, everything works great - except this creates problems down the road during upgrades and also applies the rendering choice across the whole site. I've tried some hacky jQuery like:

<script type="text/javascript">
$(document).ready(function() {
        $('head').prepend('<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" >');
         "Meta Code Ran");
 });
</script>


However, that's not working either - I'm guessing it's because the Head section gets picked up before any script can modify it.

Any tips?

Edit - seems the editor took out parts of my code the "Meta code ran" is an alert trace to let me know the code executed, and the upper address bar is just an inline javas...: document.documentMode); command.

Wells Doty Jr
Online Content Development
 
New Post
2/16/2011 5:36 PM
 
AFAIR there is a position required within meta tags, which might not be achieved by using page tags in page header.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/16/2011 5:45 PM
 
Yeah, that's what I was thinking. In the MSDN article on setting compatibility it did state that:

"The X-UA-Compatible header is not case sensitive; however, it must appear in the header of the webpage (the HEAD section) before all other elements except for the title element and other meta elements."

That's why I tried prepending it in the jQuery snippet above, but other discussions I've read say that the head section is processed before any code can be run on it.

Wells Doty Jr
Online Content Development
 
New Post
2/17/2011 3:22 AM
 
@Wells,

It's easy ;-)
The Stylehelper skin object allows you to add meta tags and specify the URL for which to add them.
http://www.40fingers.net/WeblogsNews/...

You would use "AddMetaTags" in combination with the "URL" attribute
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Single-page IE Compatibility ModeSingle-page IE Compatibility Mode


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out