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, ...DNN Nav not working in IE 11DNN Nav not working in IE 11
Previous
 
Next
New Post
12/13/2013 4:31 AM
 

The problem is that NAV uses browser sniffing and that fails for IE 11.
That's bad practice nowadays and because NAV is not developed any more, it's better to switch to DDR menu.

You can in principle edit the files to for the detection AFAIR, but I forgot where and how to be honest.
If you do that you are investing time in the past & you will have the same problem in the future. 

To be honest I never used Solpart or NAV because they were bad menu components IMHO.
Now DNN has the DDR menu which is way better (I stopped using my own menu component)
So upgrading DNN will not help (as NAV is not updated any more), only switching to another menu component does.

The switch from NAV to DDR is generally not very difficult as it can mimic most of NAVs behavior.

HTH

 
New Post
1/3/2014 3:30 PM
 

I have the same problem with a DNN 4.09.04 site. Unfortunately, upgrading is not an option at this point and DDR menu is only available for DNN 4.5 and higher. The site already uses compatibility mode, so navigator.userAgent reports as IE9. For the server side, I'm using ISAPI Rewrite to detect IE 11's user agent and rewrite the header such that it _should_ be compatible with any faulty sniffing that Solpart or other DNN modules may be doing. However, it doesn't work. I've verified that the User Agent is being rewritten properly (via log files & a simple ASPX page that prints the user agent)  but still, the menus do not appear. However, if I use IE 11's Developer Tools to change the user agent to IE9, it works fine. I've even hard-coded the rewritten user agent to exactly what IE's Developer Tools send when set to IE9 mode, but still it fails. Anyone have any ideas?

And again, I realize how terrible of a hack this is. It's a necessary stopgap until the time can be devoted to properly upgrading the site.

Thanks.

- Amir

 
New Post
1/3/2014 6:52 PM
 
DNN 4.x and 5.x are sunsetted Versions and are no longer in develpement.  You should upgrade to last Version DNN 6.x or 7.x Version also by security risks.
 
New Post
1/3/2014 6:59 PM
 
I figured out my problem. My original attempt was to simply add MSIE: 11.0 to the User Agent, since MSIE is typically what browser detection routines look for when identifying IE. As I mentioned, that didn't work, and then I resorted to using a copy-and-paste of an IE9 generated on my Windows 7 VM. The issue there was that the paranthesis were not escaped properly in the regular expression (for ISAPI Rewrite), resulting in the incorrect output. This is the configuration I'm using in httpd.conf, in case it helps anyone else who is in the same boat as me:

RewriteEngine on
RewriteLogLevel 9 # disable when satisfied it's working
LogLevel debug # same

# The following will rewrite the User-Agent header to a hardcoded IE9 one, IIF
# a) the User Agent DOES NOT contain MSIE
# b) the User Agent DOES contain Trident
# which should be sufficient in only catching IE 11

RewriteCond %{HTTP_USER_AGENT} !msie [NC]
RewriteHeader User-Agent: ^(.+)(trident.+)$ Mozilla/5.0\ \(compatible;\ MSIE\ 9.0;\ Windows\ NT\ 6.1;\ Trident/5.0\) [NC]

(note that spaces and parenthesis must be escaped in the substitution string)

Note: it'd be better if the User Agent wasn't completely hard-coded, but instead just was tweaked enough to fool the necessary modules. It seems that whatever routine is being used to parse the user agent is pretty tightly coupled to this format, so just adding MSIE: 11.0; before the trident version isn't sufficient.

- Amir
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNN Nav not working in IE 11DNN Nav not working in IE 11


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