Hi,

As a new user, I'm a bit discouraged that after investing days of setting up the enivronment and then reading through huge DNN book with lots of promises, I now find that already in "step 1", even the most basic skin fails! I'm attaching a minimal test skin with just a few lines to reproduce the problem (www.anamera.com/fileadmin/user_upload/harald/test.zip).

What's the proper procedure to pursue this? Do I report officially this as a bug?

A 5 line skin:

<%@ Control language="vb" CodeBehind="~/admin/Skins/skin.vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Skins.Skin"%>
 

<div id="ControlPanel" runat="server"></div>
<div id="skin_testing">
   <div id="ContentPane" runat="server"></div>
</div>

with a 6 line CSS:

#skin_testing
{
  width: 600px;

  margin: 0 auto 0 auto; /* Centers page horizontally */
  position: relative; /* Now child elements can use absolute positioning */
}

 will totally displace the module menus:

Hm - I haven't configured a container skin yet. My theory was, let's get ONE thing working yet, before complicating it by adding more "variables".

Also - please note that no "position: absolute" is in use in this minimal sample. I only configured the box with "position: relative" so that in my FULL skin I WILL be able to.

It get's even weirder: If you include a "STYLE="Position: Relative;" attribute in the HTML for the same box (which already has that style through the skin.css) that the behavior will CHANGE. Now THAT really makes NO sense whatsoever - there surely is some "odd" logic happening behind the scenes.

Best Regards,
Andy

Andy, I just found something out about this.

If you go to your container (I guess /portals/_Default/Containers/MinimalExtropy/Title_grey.ascx)

You will see this code:

<div class="c_head title_red">
            <div class="Head title">
                <dnn:ACTIONS runat="server" id="dnnACTIONS"  ProviderName="DNNMenuNavigationProvider" ExpandDepth="1" PopulateNodesFromClient="True" />
                <dnn:ICON runat="server" id="dnnICON" />
                &nbsp;<dnn:TITLE runat="server" id="dnnTITLE"  CssClass="Head" />
            </div>

The ProviderName="DNNMenuNavigationProvider" part will render the actions menu using the new DnnMenu.

But I just found out the Actions menu sometimes works better in combination with positioning if you use the old provider, remove red part and try if it works better.