Hello Joe and others,

My question is two fold and really don't relate to each other but decided to put them in the same thread. My first question is in regards to layering issues in DNN 6.0.1 which I believe was suppose to be the first stable version of DNN 6 in regards to upgrades. Anyway I have noticed while I have been working with DNN 6.0.1 on various client sites that a consistant theme seems to be present and that is that modules go behind things instead of infront of as they once did up to DNN 5.6.3. For example in the case of the CISS Pagepeel module when it was instantiated in DNN 5.6.3 it went over the container semi transparent title but now it goes behind it which can be seen in the fact that the green container title actually goes through my page peel module opposed to the pagepeel module going over the container.

I have also noticed in other clients I have been building web sites for that modules in which objects once were on top of other objects have all of a sudden gone behind these objects for example a more popular module out there made by mandeeps called live tabs in DNN 5 use to show the tabs protruding out of its background so it litterally looked as it you had tabs which in my case held various modules. Since upgrading to DNN 6 these tabs were not longer visable as they were behind the background and I am certain of this because I had another module on another site called engage rotator where their were tool tips that were suppose to popup when hovering over various areas of this module. I forgot if these tooltips were actually part of the engage rotator module or part of live tooltips as I had installed that module on my site as well but in any case when hovering over stuff that was suppose to invoke the live tooltip over the engage rotator it no longer displayed.

How do I know that the tooltip was working properly buried under the engage rotator? I know this because their was another area of the engage rotator that was closer to where the module background ended and a tooltip could partially be seen protruding from under this module so I know it is not a matter of these modules just not working in the new version of DNN but rather that the stacking order has some how reversed where when two modules interact with each other instead of going on top as is suppose to happen they go behind. Again this has been the case with multiple sites with multiple dynamics of interaction as one site does not have the same dynamics, same modules, etc... interacting with each other but one thing remains common to them all and that is the fact that instead of layering over they layer under. Not sure if any of your have also experienced this issue but I am thinking of posting it either in the DNN forum as well or the developers from for DNN.

Any comments or insight, or similiar experiences in this regard would be very useful to me as well as I am sure others in this community.

Thanks,

Bo

I am having exactly the same issue. My skin set was purchased from Snowcovered and it worked fine in 5.+ but it is a mess now. The menus go behind content as well as the new admin divs that open up control information. I have found a couple of suggestions online but the dont work. They suggest setting the z-index of a class name .dnnmodule. This does not solve the issue for me. The current index on that class is already 900+. I have put a ticket into Snowcovered but so far nothing. It also behave differently on different browsers. It does not seem to happen on Chrome nearly as much but the menus act strange. On Firefox it is awful and IE seems to have less menus dropping behind content but the new admin panels are a mess. This is really a disaster for us so I hope someone comes up with the fix.

For the z-index issues, it is likely that your skin uses a class name that is different than .dnnmodule. You will need to identify the actual class names used in the skin and set the z-index values appropriately.

If you have not upgraded to 6.0.1, you might try that as some errors in the furnished z-index values were fixed for some DotNetNuke things. Not necessarily for your skin.

If you are seeing the skin behave differently in different browsers, it is likely that the skin you purchased is not XHTML compliant. You may be able to work around some issues by setting the default fallback doctype to XHTML 1 in Host, Host Settings. That's not guaranteed to work. If it doesn't ask me again and I'll point you to some other things you can try.

Also, if the site is available publicly, post the URL so that I can look.

Ok you have helped a lot already! I had not thought to look at the doctype. Good news and bad. The skins I have were purchased from snowcovered.com B014 Bundle. The setting for doctype had been set to HTML legacy. The good news is that when I set the doctype to xhtml transistional or strict the admin panels all work just as they should. The menu still drops behind the content. But the huge issue is that the skins go to crap. The skin set is using tables for the content panes and when I turn it to xhtml transistional/strict the tables all squash in height and the rounded corners on the containers get lines showing where each of the pieces meet - it is a mess. If I set it to HTML legacy then the pages look right but I have the menu and admin panels are a mess. A test site we have with the issues is at http://demo1.theconnectedvision.net/home.aspx. If you go to this page and hover on the menu Contact Us you will see a menu drop down and go behind the graphic image. You can actually click this menu item even though it is behind the content but there is enough showing to click. In some of registered user pages we have multiple levels of menu and you simply cannot get to them. In HTML mode there are also other strange things such as when you move the mouse over the menu some content panes disappear. This also clears up when you go to any of the xhtml settings. It looks like this skin set is a mess but I have over 20 portals on this server and changing all of them out would be a real nightmare. It looks like the css is just bad but do you have any other suggestions? Thanks for your help - these sites have worked fine for about ayear and the update to 6.0.1 threw us into a real mess.You will need to go to the site with Firefox and IE and Chrome seem to work ok with the menus and they don't go behind the content.

What you describe is a typical thing that happens when you just switch the doctype.

The good news is that this can be fixed by going through the skin and css carefully and fixing things. It can be a painful process, but it is worth it as you end up with a site that really is cross-browser compatible.

I tried to take a look at the site, but it isn't running this morning.

Ok thanks for your input. It is clear from looking at the html of the skins it is sadly not xhtml compliant. We were working on the site and it is running now http://demo1.theconnectedvision.com/Home.aspx. If you get an opportunity to look and give me some ideas it would really be useful and I thank you for the help. I would upgrade the skins to another vendor but I have a fairly large group of users that would not be happy having to go make the changes since I cannot find another set close enough with the layot to simply change.

The old skin also used the SolpartMenu and I have upgraded a couple of pages to the DDR and it seems to be fixing the menu going behind issue.

Going forward, I think that (in spite of the difficulties) you should invest the time to make this skin runs under a doctype of XHTML 1.0 Transitional. Doing it now will save you a lot of pain and suffering over the life of the website.

Here are some comments I stole of of Jonathan Sheely's blog:

"This will make all the interface features run smoothly. Doctype may not mean much to you, but essentially it’s how your browser knows to how to read all the CSS and present the page. Margins, display types, and element alignments are the most common issues that need tweaked when the doctype is changed."

"The new admin interface (in DotNetNuke 6) uses a lot of hover and modal pop-ups. There can be fights with CSS z-indexing between your menu, content, or video, which can all be struggling to be on top. This could make your menu navigation impossible to use or leave you without the ability to administer your site if the wrong element is forcing itself on top."

I think I have a handle on this now. I have spent a few hours changing the site to xhtml compliance and I am gaining on it I think. The statement regarding admin ability being lost is true - I cannot do several things in IE but fortunately between Chrome, Firefox and IE I have been able to get through most of the challenges. I appreciate your insight and thanks for the help.

I hate to sound stupid here but how do I open a new topic? I have looked all over this interface and I cannot figure out how to make a new topic. I would like to know how to make a popup dialog like is extensively used in the 6.0.1. I have tried to do it and I believe the issue is how to reference the complete browser window because my dialogs are centering within a div but I want to center within the screen. Can you help me figure out how to open a new topic please? Thanks,
Terry

On this page -- http://www.dnncreative.com/Forum/ta...fault.aspx -- you should see a button to Add a New Topic.

There should be one on every page that lists topics for the forum.

Hello Joe,

I have been reading through this thread I had created a few days back but I still have a questin for you. It seems as though Terry's problem had much to do with the menu going under and other admin situations not working appropriately. My issue is a bit different. I think I may have the same issue in regards to XHTML compliant skin but my issue seems to be just the opposite of Terry's.

When I am logged out as anonymous user things go behind other things that should be going infront where as if I log in as adminstrator they seem to overlap appropriately. One such example can be found at the following address;

http://stevensonandco.com.dnnmax.co...ault.aspx.

Another example is at the following site: http://stamfordcommunitychurch.org/...rmons.aspx" target="_blank" rel="nofollow">http://stamfordcommunitychurch.org/...rmons.aspx

Notice here how the tabs that represent the years (found in an html module) are going behind the picture of the book which is basically the background of the live tabs module from mandeeps. The actual tabs generated from live tabs are actually behind the book totally so cannot be seen.

Also have a look at the following page: http://stamfordcommunitychurch.org/...rmons.aspx" target="_blank" rel="nofollow">http://stamfordcommunitychurch.org/...rmons.aspx

Note the page peel. Roll over it and watch what happens. Notice how the containers are bleeding through the page peel which is something that never happened before but again Joe when I am in Admin mode with all the DNN 6.0.1 ribbon bars and controls etc... the stacking or layering order seems fine.

So why is it that for me it works in admin mode but not anonymous visitor mode when logged out.

Also I was listening to the back and forth in regards to xhtml compliance and am wondering if the xhtml compliance bit in regards to the skin didn't seem to bother it in DNN 5.x why would it begin to bother it in DNN 6.0.1. Is it because of what you were mentioning about all the hover overs and modals, etc...

Anyway let me know so I can get an idea if my issues and Terry's seems to be similar.

For me the menu did go behind the flash until I beefed up the z-index on the menu item responsible for the dropdown effect from a z-index of 100 to one of 1000. Now the menu item is going over the flash but even still other modules are not interacting properly now.

I am wondering as I am talking this through on this forum if it is not as you say related to z-index issues and I am wondering if the real issue is xhtml compliance or is it this z-indexing that got scrambled when the hovers and modals were introduced into DNN 6. If it is the z-index which I suspect maybe it is would I need to go to each vendor concerning this in order to get the layering issues straightened out.

Thanks,

Bo

Ok Joe and others here is what I leanred.

In regards to the layering issue that I was experiencing it all had to do with the .dnnmodule class found in the default.css file inside your portals>_default directory.

Apparently in order to get certain module to interact apporpriately with other modules you must completely get rid of the z-index value that natively shows up in the default.css style and put their by DNN in version 6. When you do this it allows modules to work as they worked in DNN 5.

I am not quite sure why it is that in admin mode the modules work perfect even with the z-index value declared in the .dnnModule class and yet is effected in anonymous or non logged in mode. Perhaps this is a kink in DNN 6 that is yet to be worked out but if any of you are running into the layering issues similar to what I ran into this may be your answer. This solved the problem with an html module reacting with a 3rd party flash module as well as the pagepeel module interacting with another vendors module. Maybe their was a reason for this z-index declaration with in the new .dnnModule class in the _default.css file but as of yet I am not sure what it is.

Take care,

Bo

Ok Joe and others here is what I leanred.

In regards to the layering issue that I was experiencing it all had to do with the .dnnmodule class found in the default.css file inside your portals>_default directory.

Apparently in order to get certain module to interact apporpriately with other modules you must completely get rid of the z-index value that natively shows up in the default.css style and put their by DNN in version 6. When you do this it allows modules to work as they worked in DNN 5.

I am not quite sure why it is that in admin mode the modules work perfect even with the z-index value declared in the .dnnModule class and yet is effected in anonymous or non logged in mode. Perhaps this is a kink in DNN 6 that is yet to be worked out but if any of you are running into the layering issues similar to what I ran into this may be your answer. This solved the problem with an html module reacting with a 3rd party flash module as well as the pagepeel module interacting with another vendors module. Maybe their was a reason for this z-index declaration with in the new .dnnModule class in the _default.css file but as of yet I am not sure what it is.

Take care,

Bo

Whoops ... I'd missed this one.

Glad you got an answer, though!

I "suspect" that in Admin mode (which shows containers and other stuff) that some CSS styles are applied but not applied in View mode.

This is the easiest fix of all!

How to upgrade a SolPart menu»

Edit your skin's ASCX files and replace
<%@ Register TagPrefix="dnn" TagName="..." src="~/Admin/Skins/SolPartMenu.ascx" %>
with
<%@ Register TagPrefix="dnn" TagName="..." src="~/DesktopModules/DDRMenu/SolPartMenu.ascx" %>

Found here http://www.dotnetnuke.com/Resources...art_menu_3

I had the same problem but dreaded spending hours upgrading the skin.

I was on this thread in the beginning when an upgrade caused my purchased skins to go nuts. Now over a year later I had similar problems and wound up back here. I was trying to put a mega menu type function inside of a module and could not get it to work correctly. No matter what I tried the drop down kept going behind other

First, DO NOT edit default.css. Instead, override the CSS Class in portal.css or skin.css.

The reason for this is that upgrading DotNetNuke will likely replace your default.css with a new one. Then, your changes will be lost. They won't be lost if they are in portal.css or skin.css.

A good reference on z-index in DotNetNuke 6 and above is at http://dnngallery.com/blog/id/291/a...etnuke-60.

According to the reference cited above, the z-index for content should be in the 0 – 899 range.

I tried to overwrite the default.css and it simply does not work. There is something that is not obvious in what is going on with this class. By the way the link you refer to is broken at least at this moment. If you can provide the new link it would be great. Thanks,
Terry

Just remove the period at the end of the url

http://dnngallery.com/blog/id/291/a...netnuke-60