This page last changed on Nov 22, 2005 by tom@atlassian.com.

Displays the children and descendants of the current page.

Usage:
{children}
OR
{children:page=a_page_title}
OR
{children:all=true}
OR
{children:depth=a_depth}
OR
{children:depth=_a_depth_|style=heading_style}
OR
{children:_sort=<mode>|reverse=<true or false>}

parameter Required Default Description
page no the current page Specify which page to display children for
depth no none Specify the depth of descendents to display
style no none One of "h1", "h2" .... "h6" - displays children in a contents view
excerpt no false Display the child pages' excerpts (if they exist)
sort no
title
 The 'sort' attribute is an optional attribute that allows you to configure how the children are sorted. Specify 'creation' to sort by content creation date, 'title' to sort alphabetically on title and 'modified' to sort of last modification date.
reverse no false
 Use the reverse attribute to optionally reverse the sorting.

If the page parameter is '/', then the macro will list all the current space's "top level" pages - those without parents. If the page parameter is a space key followed by a
colon (e.g {children:page=DOC:}), then the top level pages of that space will be listed.

Example 1:

{children:all=true}

gives:

Example 2:

A depth of 1 will only display the first generation descendents of the current page. That is it will only display the direct children of the current page.

{children:depth=1}

gives:

Example 3:

A style of "h3" will display the page's direct children as level 3 headings, with their children as lists below the headings. Very useful for quickly generating a contents page

{children:all=true|style=h3}

gives

Child Page 1

Child Page 2

It would be nice to have a parameter 'include'. We're running into locking issues where multiple people are updating a page – we thought that an easy fix would be to have the contentious pages simply have a

Unable to render {children} Can only find children for a page, this is a comment
, and then people could just add sections by adding children. And each person would be editing independent sections. (Next we'll want to be able to reorder children)

The contention issue is that when two people edit, one persons changes get lost. There doesn't seem to be an intelligent merge capability/

Posted by marvingreenberg at Dec 02, 2005 11:18

... have the contentious pages simply have a {children:include}, and then people...

Posted by marvingreenberg at Dec 02, 2005 11:20

And, btw, the problem with excerpt-include is that it doesn't allow markup, but we may do that in the meantime.

Posted by marvingreenberg at Dec 02, 2005 11:22

Hi Marvin,

Which version of Confluence are you using? As of Confluence 2.0, there is some level of intelligent merging whereby unless there is a direct conflict between the changes made by two users, the content changes are merged.

On the same topic, we are working on further support for this concurrent editing problem for the 2.1 release. This support includes notifying people when other people are editing the page.

As for the {children:include} macro, can you please create a jira request for this at http://jira.atlassian.com

Regards,
-Daniel

Posted by daniel@atlassian.com at Dec 05, 2005 22:56

Is there a way to get a tree view (the expanding kind, with a +, as you can with the default children display)?  If not, that would be a great addition.

Posted by simonoff at Feb 16, 2007 17:21

There is an AJAX Page Tree macro that does this - you can install it from the Confluence Plugin Repository.

We'll be adding a new page tree to Builder 2.1 as seen here:

http://www.adaptavist.com/display/Dashboard

And here:

http://www.adaptavist.com/display/USERGUIDE

Posted by gfraser@adaptavist.com at Feb 16, 2007 17:27
Document generated by Confluence on Mar 22, 2007 20:54