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

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...dnn:NAV vs. dnn:SOLPARTMENUdnn:NAV vs. dnn:SOLPARTMENU
Previous
 
Next
New Post
5/19/2008 4:28 PM
 

What is the difference between dnn:NAV and dnn:SOLPARTMENU?  I am working with Effority.EALO to get my menu localized and my skin does not have dnn:NAV in it, only dnn:SOLPARTMENU.  What are the ramifications of changing it to dnn:NAV?


View Brenden Kehren's profile on LinkedIn
 
New Post
5/20/2008 4:46 PM
 
 
New Post
5/20/2008 7:50 PM
 

That gives me a bit of info.  What I want to do is localize my navigation and have the effority.ealo control but can only do it with the dnn:NAV.  Any other suggestions to do this with the SOLPARTMENT?  It appears SOLPARTMENU has more customization than the others. 


View Brenden Kehren's profile on LinkedIn
 
New Post
5/21/2008 9:22 AM
 

solpart does have a bunch more customization options "currently" Dnn: Nav is suppost to get a huge expansion / rework with the new release of DNN coming soon. Solpartmenu has a bunch of issues with moving fwd into the "web 2.0" era of xhtml, and compliance standards being the new crave. Not that it won't continue to work moving forward with the new release. It's just one of those extremely difficult items where upgrading it to handle new trends, makes it less backwards compatiable. Thus the Nav menu is going to be the stepping stone. Atleast that is how I have pieced together the random pieces of information I have got my hands on.

Someone please feel free to correct me, but I am pretty sure that is how its going to work out.

So the question becomes, do you work through having a bit less customization with NAV for the meantime, but get your localization or try and make it work with solpartmenu.

To me a boring menu that is in my own language is better then a fancy one I can't really read.

Then once we see what the new DNN release offers for its core menu you could go from there on "improving" your menu's appearance.

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...dnn:NAV vs. dnn:SOLPARTMENUdnn:NAV vs. dnn:SOLPARTMENU


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