Hi, I've created custom skins and they've been working fine for 12 months. We've recently upgraded DNN to latest version and now, when a new module is dropped in the Module Edit Menu (when hovering over the little edit triangle to the left of the module title) drops the sub-menu down below the screen. Once a module container has been applied it works ok again and the edit options menu appears in place - however our typical admin users will not be able to get that far because they won't see the menu below the screen.

I've pulled apart both the skin and the CSS to isolate the issue. I'm sure it is related to my skin using container divs (with nested divs) using "position: relative". When I remove this attribute from the related style in the SKIN.CSS the issue is resolved, however my page layout is totally screwed up and I can't get it to work without using relative positioning.

I have tried hundreds of adjustments in both the SKIN.CSS and DEFAULT.CSS to try and resolve. But no luck.

I can post bits of code and/or screen grabs but can't direct you to the site because it's behind a firewall.

PLEASE HELP!!! I've been trying to resolve this all day! Going crazy.

Thanks,
GeekGirl

Thanks very much for the response. I didn't realise that 'solpartmenus' were used as standard. I've seen heaps of posts related to this. I thought it was a different issue.

Anyway, I created a default admin skin but I'm not sure if I've set it up properly.

Do I go to "Site" settings then under "Appearance" select the default container from "Admin Container" and check 'host' ???

I can see the styling change when I actually go into the container edit but the action menu is still dropping below screen.

I'd like to try this solution first. Also, I'm not sure exactly what you mean by the 2nd solution. Where do I change from [ACTIONS] to [DROPDOWNACTIONS]... please don't tell me this is a manual change.

Cheers,
GG

I've managed to make things dissappear behind other things by getting my z-indexes the wrong way round - have you got z-index issues? Even if you're not specifying z-indexes directly it will still be relevant with the stacking contexts created by the relatively positioned divs. Does it go wrong in all browsers, or just some?

Rhys.