Forum Tags

Hi, i've many skins using PageLocalization 2.0.4 and MLMENU

Which advantages i have converting my skins from PageLocalization 2.0.4 & MLMENU to PageLocalization  3.0.2 & MLNAV ?

Thanks

Mauro

MLNAV is derived from the more standard DNNNAV menu, which means that your pages will render more xhtml compliant.

ALso, the userinterface of PageLocalization 3.0 is much easier to use (as it uses a tree view)

finally, PL 3.0 has a page redirection solutions, which means that you can now redirect pages based on language

I've tried to convert my MLMENU to MLNAV but i've seen that the parameters are very different !
do you know how to convert it ?
This is my actual Token:
[MLMENU]


usearrows
false


userootbreadcrumbarrow
false


usesubmenubreadcrumbarrow
true


separator
]]>


rootmenuitemlefthtml

]]>


rootmenuitemrighthtml

]]>


rootmenuitemcssclass
rootmenuitem


rootmenuitemselectedcssclass
rootmenuitemselected


rootmenuitembreadcrumbcssclass
rootmenuitembreadcrumb


submenucssclass
submenu


submenuitemselectedcssclass
submenuitemselected


submenuitembreadcrumbcssclass
submenuitembreadcrumb


CSSNodeSelectedRoot
rootmenuitembreadcrumb


CSSNodeSelectedSub
submenuitemselected



thanks for help

Mauro

MLNav (equivalent to DNN Nav) is NOT compatible to MLMENU (equivalent to SolpartMenu), please do not just upgrade the one with the other!. For more information about DNN Menu skin objects, please check out the DNN skinning documentation