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:
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.