I used dnn version 5 previously. Now i upgraded it to dnn6 community edition. The error is

1) I am using vertical menu skin for my website. Beside to menu i have the container with image in it. The menus subpages are been displayed behind the container and we are not able to see it.


2) Another problem is when i tried to edit the data in the container. A popup window appears, with fckeditor in it, i hope this is the latest feature in dnn6 . I tried to add a image into my data, when i click on the image icon of fckeditor the linking popup window is been displayed behind the popup window of fckeditor. I was not able to add a image or link any pages as the popup windows are not been able to view.

I tried it in both ie8, and google chrome.

1. I believe that this is related to a "z-index" issue in the CSS files. If you upgraded to 6.0.0, it may be that this is solved simply with a further upgrade to 6.0.1. You can check the DotNetNuke Wiki at DotNetNuke.com and search for z-index for more information. You can also fix this by defining the z-index for some specific CSS classes.

2. This is probably a manifestation of the same issue. Yes, version 6 of DotNetNuke uses lots of modal popups instead of separate pages. You can turn this off with a setting available in Host Settings .

1) I had not found the Solution for z-index. Please help me if their is any way to solve this issue.

2) I am using the version 6.0.1 only. I had turned off the popups. The turn off option is in admin settings but not in the host settings.

Yes, the option to turn off popups is specific for the portal, so is adjusted on the Admin, Site Settings page.

The solution that you seek requires setting the z-index for some CSS classes. Have a look at the Wiki at DotNetNuke.com and search for z-index. You will find some discussion there that, hopefully, helps you fix this problem. If you are using a custom skin and/or containers, there may be additional classes that you will need to adjust.

You may find the techniques outlined in our :Troubleshooting DotNetNuke Skins" tutorial. Note also that both Chrome and IE now have built-in tools that let you inspect and modify (on the fly) CSS classes. Hit F12 to get to them.