MSPSS: is there life after the helpdesk?

sharing solutions to uncommon IT problems

DotNetNuke – Upgrade to 7.1.1 – DDRMenu doesn’t work anymore

with 5 comments


Hello,

After upgrading DNN PE to 7.1.1, the DDRMenu suddenly stopped working due to a JS error: “Uncaught TypeError: Object function (e,t){return new b.fn.init(e,t,r)} has no method ‘curCSS'”.

the JQuery CurCSS method has been deprecated in JQuery 1.8.

DNN 7.0.x used JQuery 1.7 while DNN 7.1.x uses JQuery 1.9.1

The DDRMenu has not been updated to work with new versions of JQuery and they don’t seem to have a new version in the pipe on their website http://dnnddrmenu.codeplex.com/

The fix is quite easy but it might get overridden next time we upgrade the DDRMenu:

Edit \DesktopModules\DDRMenu\DNNMenu\DNNMenu.min.js and replace all “curCSS” method calls (2) with “css”

Update: DNN support replied that everything worked fine with a “out of the box” skin and therefore the problem was caused by my custom skin which was out of support (they don’t give support on Skin development).
By comparing my skin with one of the OotB, we found out that we were using <DNN:NAV instead of the more common <DNN:MENU. The DNN:NAV should still work but I get a feeling that is slowly dying (I can only find documents related of this menu in connection with DNN4 and 5, nobody seems to have used it since…)

We will investigate further but in the meantime, we are considering switching our menu to <DNN:MENU

Update2: Replacing the DNN:NAV with a DNN:MENU was easier than I thought and I get the feeling this incompatibility is the tip of the iceberg. Your safest bet is to download a free, prebuilt menu (superfish works pretty well out of the box), copy it in the skin folder and link it from the template (menustyle) and tweak the look and feel.
FYI: here is what they write on the DNN website about DNN:NAV:
Note that while it is also possible to use a dnn:NAV control with the DDRMenuNavigationProvider and CustomAttributes to render a non-DNNMenu template, it adds complexity and brings no particular benefits, so is not recommended.

HTH,

Roberto.

Advertisements

Written by zantoro

September 18, 2013 at 12:01 pm

Posted in DotNetNuke

Tagged with , , ,

5 Responses

Subscribe to comments with RSS.

  1. wish that fix worked for me, but it didn’t

    Sean

    October 1, 2013 at 6:26 pm

    • Hey Sean,
      sorry to hear that, however, since I wasn’t happy with the workaround and since more problems came up along the way, I decided to open a support ticket with DNN… I have a call scheduled tomorrow and I’ll keep you posted.

      By the way: have you tried to reference the old JQuery 1.7? you can find the setting in Host -> Host Settings -> Advanced settings -> JQuery (remember to check the “use hosted…”)

      zantoro

      October 1, 2013 at 8:10 pm

      • Thanx for the reply and please do keep me posted. I do not really want to have to develop a new menu as I use this menu on about 15 web sites!!!

        Sean

        October 1, 2013 at 8:20 pm

      • Yes, I just discovered this problem myself. Please keep us posted

        David Jamell

        December 19, 2013 at 7:47 pm

      • Yeah, it’s quite annoying but you do have a couple of choices:
        1. Downgrade the DNN default JQuery (in the host advanced settings) to 1.7.1
        2. Switch to DNN:Menu (easier than it sounds…)

        zantoro

        December 19, 2013 at 8:54 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: