Hi everyone

This change to z-index has the smell of "untested", like a few other bugs with DotNetNuke upgrades. It's annoying that things like this is not sorted out completely before a major release.

Here is a solution (or at least what works for some of my portals)

DNN added a z-index to 3 areas: 902 to all modules, 906 to the actionmenu for each module and 1000 to the ribbonbar. I have no idea as to why they've select that high values, since most skins use values below 100.

What works is, to make sure your menu container is above the module z-index and below the ribbon z-index, and the submenus above actionmenu index. It's up to you to choose if you want to change the DNN files, your skin files or both.

My solution is to change the DNN files:
Portals/_default/default.css line 231: change .DnnModule z-index from 902 to 2
Portals/_default/default.css line 232: change .dnnActionMenu z-index from 906 to 6
Portals/*your-portal*/skins/*your-skin*/skin.css: menu-container z-index: 5
Portals/*your-portal*/skins/*your-skin*/skin.css: menu-sub-container z-index: 10
*if you have a vertical menu or other menus, do the same for those

That fixed the z-issues on some of my portals. If you know your menu has a specific z-index value (like when Artisteer creates them), make sure you change the DNN z-index values to lie below the menu z-index values and the ribbonbar to above it.

I'd wish the DNN crew would include some artiteer testing in their future updates to avoid issues like this one. Remaking the admin interface like this is bound to have a nasty effect on third-party solutions like Artisteer skins.

I hope this helps those that haven't found a solution yet :)

Kind Regards
Rune

 You have to describe what your problem is then...

If it's an object (like a flash header), you might need to add the parameter wmode="opaque" to the object ;-)

/Rune