Broken DNN site using vertical menu

So you finally got DNN running and now playing around with the skin and thought you’d try the vertical menu in you DotNetNuke 4.4.0 and 4.4.1 build..
Lucky you – you just struck the jackpot of not having the correct files to run that menu..

Were you one of the many who thought this was a skin bug??? well it’s not!!
Were you one of the many who thought you had to reinstall DotNetNuke, and did what one person ended up doing to try and remove the problem??? That poor person reinstalled DotNetNuke 4 times… because the files weren’t there..

But the good news is – it’s a dead easy fix…

Simply replace the skin – the vertical menu skin that’s gone foobar with a renamed correct one.. Once you’ve uploaded via FTP hit the refresh button and your skin will be fixed.

And for those who thought you need to reinstall DotNetNuke – sorry about that, but there is another build coming out which hopefully won’t have the same problems.

And another helpful tip –
CREATE A SEPARATE TEST PAGE, AND NEVER TEST ANYTHING NEW ON YOUR HOME PAGE!!

When testing skins, always create a new page, and add the skin to preview it first.. DO NOT set a skin you’ve never used or seen through the admin / settings page.

However, the fact this bug is caused by the build, and no other reason, that is just a case of unlucky!

Nina Meiers

4 Responses to Broken DNN site using vertical menu

  • Steve McLenithan

    This just fixes a dead home page and doesn’t actually provide the vertical menu. Is there a fix to get the vertical menu support back?

    Reply
  • Steve McLenithan

    Sorry to spam, but I found the fix. The DLL that was left out of DNN 4.x build is:
    DotNetNuke.DNNTreeNavigationProvider.dll

    If you replaced the vertical skins with copies of the horizontal one, you will need to get the originals from the zip file. You can get DotNetNuke.DNNTreeNavigationProvider.dll from DNN 3.3.7 Install’s bin directory. Of course this is a hack and I have no way of knowing if this dll has changed with the 4.x release so do this at your own risk. Worked for me though :)

    Reply
  • Nina Meiers

    Steve, Thanks for posting this – I wanted to check a couple of things before I posted anything different but you’re right – putting the old providers back in solve the problem.

    I appreciate your input.

    Nina

    Reply
  • Jason

    Thanks to both of you! :) You saved me a re-install! :)

    Jason

    Reply

Leave a Reply

Post Comment