From 543cd86f748b9086b9284ff27cf3928776887d8b Mon Sep 17 00:00:00 2001 From: romanb Date: Wed, 5 Sep 2007 16:14:08 +0000 Subject: [PATCH] Fixed typo in the docs --- manual/new/docs/en/hierarchical-data/nested-set.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/new/docs/en/hierarchical-data/nested-set.txt b/manual/new/docs/en/hierarchical-data/nested-set.txt index 7a5a051d3..7d2db6ef7 100644 --- a/manual/new/docs/en/hierarchical-data/nested-set.txt +++ b/manual/new/docs/en/hierarchical-data/nested-set.txt @@ -176,7 +176,7 @@ $numDescendants = $record->getNode()->getNumberDescendants(); // returns the num getDescendants() and getAncestors() both accept a parameter that you can use to specify the "depth" of the resulting branch. For example getDescendants(1) retrieves only the direct descendants (the descendants that are 1 level below, that's the same as getChildren()). In the same fashion getAncestors(1) would only retrieve the direct ancestor (the parent), etc. getAncestors() can be very useful to efficiently determine the path of this node up to the root node or up to some specific ancestor (i.e. to construct a breadcrumb navigation). -++++ Simply Example: Displaying a tree +++++ Simple Example: Displaying a tree ...