We have some older websites that are still using the basic solpart menu - and in IE 10, the menu doesn't show up at all. (sample site: www.kearneykidzone.com)

We did some testing and were able to fix it by changing it to the DDR Solpart - but then it doesn't show up when you are logged in. Somehow, some CSS was being added to not display that div. So, I added CSS to overwrite the "display: none" to fix that issue, but the menu then doesn't have any styling or functionality - it's just displayed in one long unordered list. Everything looks/works fine when you are logged out - it's just when you are logged it that we are seeing the problem.

Do you have any other ideas as to how we can fix the basic solpart menu? Or do you have any idea how we can change it to the DDR without losing the styling/functionality when you are logged in?


Also, we are having trouble logging into sites in IE 10. The popup works fine but after you enter your credentials, you can't hit enter and you can't click on the login button.

Have you gotten much of this fixed? I looked at the http://www.kearneykidzone.com/ site with IE and with Chrome and both look ok. I see the menus in both browsers.

On the home page and with IE10, the left-hand menu doesn't appear. Clicking the compatibility mode button makes it appear. That might indicate and issue with the z-index of the menu items. Is the left menu being done with DDR also?

Not sure about the login issue, but try it in compatibility mode.

Also, which version of DotNetNuke is this?

And ... you might want to update the copyright date to 2013.

Sorry... I guess I should have been more specific when I listed that site. That particular site is using the solpart menu on the left side - the top menu is just static links in the skin. I haven't made any changes to that particular site so it's still using just the basic old solpart.

If you inspect the code you can see that the menu is just xml code so I don't think it's a z-index issue. It just appears to not have any styling being applied to it.

Another example would be miller-engineers.com - their top menu is just non-existent.

Because it's on a variety of sites, all of the DNN versions are different. Some might be in 6, some in 5, some even in early 5.

Login works in compatibility mode. Is this a known issue? And is that probably going to be the only solution?

Thanks!

You could try adding a meta tag to force IE9 compatibility. You can do this in your skin:

That sounds like an easy solution! Do you have an example of how to do that?

If your sites are sufficiently up to date to use the 40fingers Style Helper Skin Object, it's rather easy. There are step-by-step instructions here:

http://www.40fingers.net/WeblogsNew...er-10.aspx

I'm not sure if this is compatible with DNN 5.x. If not, you may be able to use Will Strohl's Content Injection module -- http://wnsinj.codeplex.com/ -- just look for an early version that's compatible with the DNN Version that you are using.

Let me know if that works for you.

But ... there are quite a few reasons that you should get those old sites updated ...

Thanks for the info! We tried using the 40 fingers module on this site: miller-engineers.com - and on all the machines I've tested it on, it works fine. It hides the compatibility button and forces the site to IE 9. However, on the client's computer, it doesn't seem to be working. They still see the compatibility button and don't see the menu. They have a windows 7 machine with their IE 10. Do you know of any oddities that it would be behind it not working on their end? They've tried hard refreshes, restarting their computer, clearing their cache/history - not sure what else to try!

Pull up the developer tools (F12) on the client's computer, and make sure that they haven't set it to some other mode.

Can you elaborate a little more? Not sure what you mean by "some other mode".

If you hit F12 in IE, that brings up the Developer Tools. Part of that is the Browser Mode and the Document Mode. Make sure that they are set to IE10 and Standards mode.

Sometimes these settings can be sticky, so it's important to make sure to start in the IE10/Standards mode.

Okay great! Thank you!

I should have mentioned that having a doctype attached to your skin files also helps. You should also set the Fallback Doctype in Host Settings to XHTML 1.0 Transitional or HTML.