Apollo Software Normal layoutMedium LayoutLarge Layout    Normal TextLarge Text
Home | DotNetNuke | About ... | Downloads | Forum | Blog
United States Netherlands
Register | Login

Forum Tags

 
boolean   error   file   help   just   language   menu   mlhtml   module   modules   need   object   page   pagelocalization   problem   site   skin   string   version   work  

  

Need live support?

Please feel free to add my support e-mail address to your MSN contacts. If you catch me online, I'll be able to solve your problems faster than through this forum. Please appreciate that I only give free support on our own modules!

My msn account: support@apollo-software.nl. Alternatively, you can click the botton below, it will open up a Live Messenger window (Windows Live ID required)

  

The voice of menu not change..
Last Post 2009-06-23 12:15:52 by erikvb. 7 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
grenzo
New Member
New Member
Posts:25

--
2009-06-06 10:14:27  
Hem, I had wrong forum..

I have installed:
1) Apollo.modulelocalization.PA.02.00.04.zip
2) Apollo.MLHTML.01.03.03.zip
3) Apollo.PageLocalization.PA.02.03.00.zip

The text in the modules mlhtm change language,
But the voices of menu, changed with pagelocalization, not.

Why?
Where I wrong?
Thanks
grenzo
New Member
New Member
Posts:25

--
2009-06-06 10:15:14  
Ah,
I use the default skin of DNN 04.09.04...
erikvb
Advanced Member
Advanced Member
Posts:713
Avatar

--
2009-06-07 16:31:45  
hmm.. not sure what you mean by "voices of menu"....
Erik van Ballegoij,
a view from my attic, my personal blog

The personal blog of Erik van Ballegoij

grenzo
New Member
New Member
Posts:25

--
2009-06-08 07:37:25  
Hem.. *voci del menu* in Italian.. are precisely the menus..
grenzo
New Member
New Member
Posts:25

--
2009-06-22 14:23:25  

I have the skin of default: minimalextropy, I have changed this text from the file: index full.ascx :

<%-- pre Apollo
<%@ Register TagPrefix="dnn" TagName="NAV" Src="~/Admin/Skins/Nav.ascx" %>
--%>
<%@ Register TagPrefix="dnn" TagName="NAV" Src="~/DesktopModules/PageLocalization/MLMenu.ascx" %>

but DNN gives error...

Where I wrong? Apollo is not compatible whit Skin Object NAV ?

Thanks...
erikvb
Advanced Member
Advanced Member
Posts:713
Avatar

--
2009-06-22 18:50:58  
What error do you get?



Erik van Ballegoij,
a view from my attic, my personal blog

The personal blog of Erik van Ballegoij

grenzo
New Member
New Member
Posts:25

--
2009-06-23 12:00:43  
I am sorry but I have already deleted the installation.

was I had done wrong?

Apollo work with the tag NAV?

Why many skins use the tags solpartmenu and only a few use the tags NAV?

Thanks
erikvb
Advanced Member
Advanced Member
Posts:713
Avatar

--
2009-06-23 12:15:52  
> Apollo work with the tag NAV?
yep it does. You just have to use MLNAV, which is identical to NAV, except it is multilingual

> Why many skins use the tags solpartmenu and only a few use the tags NAV?

Not sure I should answer that question J, there can be many reasons:

· Support for older dnn versions (MLNav is available from dnn 4.6 if memory serves me correctly…..)

· When the customer doesn’t care about XHTML (SOLPARTMENU can not be made xhtml compliant, NAV can)

· Lack of knowledge of latest level of skinning technology in DNN

Pick your choice J



The proper way to add MLNav to your skin is this:



1. Register the control:



<%@ Register TagPrefix="dnn" TagName="MLNAV" Src="~/DesktopModules/PageLocalization/MLNav.ascx" %>



2. Use it somewhere in the skin:

<dnn:MLNAV runat="server" id="dnnNAV" ProviderName="DNNMenuNavigationProvider" IndicateChildren="false" ControlOrientation="Horizontal" CSSNodeRoot="main_dnnmenu_rootitem" CSSNodeHoverRoot="main_dnnmenu_rootitem_hover" CSSNodeSelectedRoot="main_dnnmenu_rootitem_selected" CSSBreadCrumbRoot="main_dnnmenu_rootitem_selected" CSSContainerSub="main_dnnmenu_submenu" CSSNodeHoverSub="main_dnnmenu_itemhover" CSSNodeSelectedSub="main_dnnmenu_itemselected" CSSContainerRoot="main_dnnmenu_container" CSSControl="main_dnnmenu_bar" CSSBreak="main_dnnmenu_break" />



Mind you: when working with ASCX skins, even then, it is good practice to use the same Tagname as the registered name of the menu



Of course, when using HTML skinning, you just put the [MLNAV] token in your skin, the rest happens automagically when the skin is parsed. In a DNN 5 skin that would look like this:

<object id="dnnNAV" codetype="dotnetnuke/server" codebase="MLNAV">

<param name="ProviderName" value="DNNMenuNavigationProvider" />

<param name="IndicateChildren" value="false" />

<param name="ControlOrientation" value="Horizontal" />

<param name="CSSNodeRoot" value="main_dnnmenu_rootitem" />

<param name="CSSNodeHoverRoot" value="main_dnnmenu_rootitem_hover" />

<param name="CSSNodeSelectedRoot" value="main_dnnmenu_rootitem_selected" />

<param name="CSSBreadCrumbRoot" value="main_dnnmenu_rootitem_selected" />

<param name="CSSContainerSub" value="main_dnnmenu_submenu" />

<param name="CSSNodeHoverSub" value="main_dnnmenu_itemhover" />

<param name="CSSNodeSelectedSub" value="main_dnnmenu_itemselected" />

<param name="CSSContainerRoot" value="main_dnnmenu_container" />

<param name="CSSControl" value="main_dnnmenu_bar" />

<param name="CSSBreak" value="main_dnnmenu_break" />

</object>



Erik van Ballegoij,
a view from my attic, my personal blog

The personal blog of Erik van Ballegoij

You are not authorized to post a reply.

Active Forums 4.1
NOT LICENSED FOR PRODUCTION USE
www.activemodules.com
  

Copyright 2002-2007 Apollo Software
Terms Of Use  |  Privacy Statement
Page generated in 1.6412865 seconds.