Best practice for getting the number of children nodes
WaltzKing Beginner grinnerPosts: 3Registered Users Beginner grinner
I have an application where in a couple of places I need to enumerate through all of the children of a node looking for a particular child, based on some property of the child (in one case the child's name and in another case the child's URI). Is there a "best practice" way of making sure I iterate through _all_ of the children? The reason I ask is that I've noticed that fetching the children of a node has defaults on the number of children returned - 100 in the case of nodes that are images and 10 in the case of nodes that are galleries. Alternatively, is there a way of finding the desired child node directly without the iteration?