DotNetNuke missing menu navigation for FireFox version 17

Question

We have a DotNetNuke app with a DNN Menu.

Recently, after updating to FireFox version 17 we found that the whole DNN Navigation Menu is invisible. In other browsers it is fine, and it also works fine in FireFox 16 and earlier versions.

Does this have anything to do with the browser settings?

check if there are any javascript errors, if any paste here – Prashant Lakhlani Nov 27 '12 at 07:29 — Prashant Lakhlani, Nov 27 '12 at 07:29
I don't find any JS errors, I saw using FF debugger – phani kumar Nov 27 '12 at 09:25 — phani kumar, Nov 27 '12 at 09:25

score 1 · Answer 1 · answered Nov 28 '12 at 15:46

1

Firefox changed their user agent string. Here's the fix: http://www.dotnetnuke.com/Community/Community-Exchange/Question/2733/Firefox17-Bug-How-to-change-User-Agent-String.aspx

answered Nov 28 '12 at 15:46

Rochelle

19
1

1

Could you add the basics of the solution on the linked page? That way if the [link rots](http://en.wikipedia.org/wiki/Link_rot) this answer will still help future visitors. – Jeroen Nov 30 '12 at 10:59
This link no longer goes to a how-to. – Dewayne Oct 24 '13 at 02:10

Secondtoe · Answer 2 · 2012-11-29T20:12:54.627

We found a solution that may help. Our menu was displaying, but expanded the entire thing out as an unordered list. We're on DNN 5.6.0 and using the DNNMenuNavigationProvider.

We installed the DDRMenuNavigationProvider here: http://dnnddrmenu.codeplex.com/

With detailed instructions here: http://www.dotnetnuke.com/Resources/Wiki/Page/DDRMenu-user-guide.aspx

We simply then went into the skins and updated the same dnn:NAV controls to use the ProviderName="DDRMenuNavigationProvider" and the menu came back the way it was, with an extra sliding flyout animation.

Hope that helps.

Update In addition to updating the navigation provider, and the user agent as described above, we also updated the \js\ClientAPICaps.config file based on these instructions: http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=13964&PROJID=2

We reverted the update for the dnn:NAV controls back to DNNMenuNavigationProvider and everything went back to the way it was operating before.

score 0 · Answer 3 · answered Dec 04 '12 at 08:05

0

Firefox released a patch, 17.0.1, which fixed this (for now) for my situation. This bullet item from the release notes is about this issue:

17.0.1: Reverted user agent change causing some website incompatibilities.

answered Dec 04 '12 at 08:05

Jeroen

60,696
40
206
339

DotNetNuke missing menu navigation for FireFox version 17

3 Answers3