tree

The Tree Tag makes it possible to show a piece of the MMBase cloud generically. This tag never works alone. Firstly, it will try to find a surrounding `treecontainer' tag, which defines the `starting query' and other the properties of this tree. If there is no surrounding tree-container tag, then it can also use one of the other node list containers (relatednodescontainer and listnodescontainer) to define the `starting' query. If also that does not succeed then it will start looking for any surrounding node-provider (such as relatednodes, listnodes and node) and will use the provided node as a base for the starting query of the tree.

If you want to define the surrounding node-provider with a container, then you can use the 'node' attribute to enforce it to use the node-provider and not it's container.

• type
  The tree will grow with path-elements of this type.
  see: type attribute of relatednodes
  
• role
  The path-elements will be connected by relations with this role.
  see: role attribute of relatednodes
  
• searchdir
  This is the directions in which the relations must be followed (destination or source).
  see: searchdir attribute of relatednodes
  
• maxdepth
  To avoid coming into an infinite loop (which is possible because mmbase data is not actually structured as a tree, but as a `network' of nodes), there should always be a `maximal' depth to which relations are followed. This defaults to 5.
  see: orderby attribute of treecontainer
  
• orderby (since: MMBase-1.7.1)
  It is possible to order the elements of a level of a tree by using the `orderby' field. If you wish to order using the fieldvalue of the relation from one level to another, prefix the field with the builder name or role(for example: "categories.title" or "posrel.pos"). You can order by more fields, by comma-separating their names.
  see: orderby attribute of list
  
• directions (since: MMBase-1.7.1)
  Sort orders for the `orderby' arguments (comma separated `up' and `down'). This list may be shorter than the list of `orderby'. Missing directions are defaulted to the last specified one.
  see: directions attribute of list
  
• max (since: MMBase-1.8.1)
  see: max attribute of list
  
• varStatus (since: MMBase-1.8.6)
  see: varStatus attribute of listprovider
  
• varBranchStatus (since: MMBase-1.8.6)
  This provides information about the current looping status of the current branch. If e.g. you want to know if the current node is the last of the 'branch', then you could use 'varBranchStatus="branch"'> ... .
  see: varStatus attribute of listprovider
  

• container

• jspvar
• commitonclose

• comparator
• add
• retain
• remove
• varStatus

• node

• referid

• id

• context