Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIDNNmenu - canDNNmenu - can't accomplish anything with it?
Previous
 
Next
New Post
12/8/2008 11:27 PM
 

Hi,

I started my quest to use the DNNmenu in DNN 4.9 in the Skinning Forum - but from what I gather, everyone there seems to have given up on DNNmenu and is pointing me to functioning third party solutions (which I do appreciate, as this may be the way I ultimately will have to go).

But call me stubborn/naive: Considering that DNNmenu is the official/supported replacement of the SolPartMenu (which implies to me that it ought to be very stable and mature), I thought I was acting quite responsible and reasonable to expect that DNNmenu should AT LEAST work for even the most basic of all skins that one can dream up.

Hopefully, posting here will either lead to someone pointing out MY error (since there is no documentation where I could help myself), or point me to the proper procedure that I'm supposed to follow to report the issues as official bugs so that a patch/update can be released.

In the following screen shot you'll notice the following "issues" (I inserted background colors into the CSS to easily show the size of each element):

a) The submenus are totally out of visual context of the main menu, shifted down AND to the right. The page's main DIV container has position:relative - but there is NO absolute positioning (yet) in that most basic of skins.  I've since read in this forum that other's have already reported this for a while - but I can't quite believe that a major usability impairment of a key feature of any product (it's main menu) would not be given the highest priority? What good is any product if you can't even get the menu to work?

b) The "green" background is the "CSSControl". It has a style of HEIGHT and LINE-HEIGHT of 22 px - both settings have no effect in standards mode

c) The "blue" background is the  "CSSNodeRoot". In utter desperation I also gave THAT a style of HEIGHT and LINE-HEIGHT of 22 px - no such luck in standards mode.

Which style is the correct one to set the height so that the background of each root node will extend to the full height of the menu bar (in my case 22px)?

Screenshot of DNNmenu issues

Here the skin and CSS that goes with that example:

<%

Control language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Skins.Skin" %>
<%
@ Register TagPrefix="dnn" TagName="NAV" Src="~/Admin/Skins/Nav.ascx" %>
<div id="ControlPanel" runat="server"></div>
<
div id="skin_testing">
 
<div id="skin_MenuBar">
 
<dnn:NAV runat="server" ID="dnnNAV"
    ProviderName="DNNMenuNavigationProvider"
   
IndicateChildren="true"
   
ToolTip="Title"
   
CSSControl="Main_DNNMenu"
   
CSSNodeRoot="Main_DNNMenu_NodeRoot"
   
CSSNodeHoverRoot="Main_DNNMenu_NodeHoverRoot"
   
CSSContainerSub="Main_DNNMenu_ContainerSub"
   
CSSNode="Main_DNNMenu_Node"
   
CSSNodeHover="Main_DNNMenu_NodeHover"
  
/>
 
</div>
 
<div id="ContentPane" runat="server"></div>
</
div>

#skin_testing

{

 

 

width: 600px;margin: 0 auto 0 auto; /* Centers page horizontally */

 

position: relative; /* Now child elements can use absolute positioning */

}

#skin_MenuBar

{

 

 

 

}

width: auto;height: 22px;background: red;

*.Main_DNNMenu

{

 

 

 

}

height: 22px;line-height: 22px;background: green;

*.Main_DNNMenu_NodeRoot

{

 

 

margin: 0 1em 0 0;padding: 0 1em 0 1.2em; /* Space between menu items */

 

 

 

 

 

}

font: bold 11px tahoma, arial, helvetica, sans-serif;color: White;background: blue;height: 22px;line-height: 22px;

*.Main_DNNMenu_NodeHoverRoot

{

 

}

color: #9f9f9f;

 
New Post
12/9/2008 9:27 AM
 

a)  I *think* this issue has been resolved in the latest version of the menu included in dnn5.  Positioning of elements that have relatively positioned parents is not an easy calculation as the parent node tree's offsets needs to be walked and the combinations of parent offset.  If you could verify that your issue is still present in dnn5 b2 it would help.  If not, then I would ask what is the need to set the relative positioning of the root element?

b)  Not sure if your complaining about the menu here or css in general.  Obviously I have no control over how css gets interpreted.

c)  Same as b.  However, I believe your issue may lie in the fact that those line items are spans, and therefore not block elements, and therefore cannot have their heights set, unless converted to block elements (display: inline-block or block). 

Finally, the issue tracker for the webcontrol project is located here:  http://support.dotnetnuke.com/project/Project.aspx?PROJID=39


 
New Post
12/9/2008 11:10 AM
 

Dear Jon:

Thank you for taking the time to respond.

Once I'm past the "skin" phase (where I can pass on the content work to other staff), I'll install DNN 5 and retest this problem to confirm that it's fixed. I see that the new version finally allows us to do away with tables and appropriately use unordered lists - which hopefully will eliminate many ambiguities and we won't have to rely on ASP.NET version correctly identifying every single search engine robots/spider (which it does not).

As far as the "height" issue: The text in your SPANs will react to "line-height" - that's what drove me crazy. But, after some more testing I encountered a REALLY strage oddity:

line-height: 22px;
font: bold 11px Tahoma, Arial, Helvetica, sans-serif;

will NOT recognize the height, but:

font: bold 11px Tahoma, Arial, Helvetica, sans-serif;
line-height: 22px;

will.

I am baffled by the fact that the ORDER of these two style settings would have any effect, and I'm not sure who to fault for this (I was falling asleep, so it was too late to see if it was consistent in different browsers) - but, at least I worked around that problem.

As far as the page container being set to "position: relative" is simply so that I can use absolute positioning for certain sections. If it wasn't for the control panel, I could have let it default to the <body> viewport. The idea is to move the most relevant data of the page (the actual headlines and content) to the TOP of the page to let spiders comprehend it as the most relevant information that should be indexed/weighted that way - while moving less specific/generic HTML code (such as the header/banner/log/menus etc) to the bottom of the HTML code.

Best Regards,

Andy

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIDNNmenu - canDNNmenu - can't accomplish anything with it?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out