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, ...DDRMenu INodeManipulator and FindNodeByNameDDRMenu INodeManipulator and FindNodeByName
Previous
 
Next
New Post
12/18/2011 4:46 PM
 

Has anyone noticed that when using MenuNode.FindNodeByName() that any node found does not have Children populated when indeed the Tab on the site has children? I've run into this problem trying to aggregate children from many menu nodes into another node. However, when trying to access the found node's children, there are none. Any ideas?

...
            MenuNode foundNode = node.FindByName(name);
            if (foundNode != null){
                foreach (MenuNode thisNode in foundNode.Children){
                    _tmpList.Add(thisNode);
                    if (thisNode.HasChildren()){
                        // recursively call again...
                    }
                }  
            }

....

foundNode.Children is always empty when there is certainly child Tabs present within that DNN Menu Node. I'm wondering if there is a problem when converting from DNNMenuNode to DDRMenu Node types (I noticed that occurs at some point).

 
New Post
12/18/2011 5:11 PM
 

[EDIT]

Just to reiterate the issue, I am attaching images of 1) The node found while debugging that shows there are no children and the TabId of the node. Then the SQL query which uses that same ID as the parentId to show there are indeed 5 children.

DEBUG:

Photobucket


SQL:

Photobucket

 
New Post
12/18/2011 5:40 PM
 

[UPDATE]

Appears this is not just within FindNodeByName, it's any node 3 levels deep. It appears children are not populated past the 2nd level.

 
New Post
12/18/2011 6:45 PM
 

[RESOLVED]

It would help if I selected more than two levels in the NodeSelector property of the skin object. yes, My bad. Always something ridiculously simple. 

NodeSelector="*,0,2" is what I had and of course, can't manipulate data I specifically told the menu not to get. Geez!

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DDRMenu INodeManipulator and FindNodeByNameDDRMenu INodeManipulator and FindNodeByName


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