2.10.3 Navigation component

• the query node has been completely rewritten to allow some powerful new features:

• it is now possible to select multi-value values (which was previously not the case).
• it is possible to select the new hierarchical values. This will build up hierarchical structures corresponding to the hierarchical field values.
• when selecting link values (as non-last selected value), document nodes will be created instead of group nodes.
• sort order and visibility can now be configured for each selected value.
• query nodes can now have child nodes, the child nodes will be executed for each query result. This allows for things like importing all navigation trees satisfying a query, nested queries, building link nodes dynamically, ...

• navigation trees can now be generated (expanded) up to a certain depth. In the Wiki, this is configured with a new element <navigationDepth> in the siteconf.xml. This makes it possible to have a navigation tree expanded up to e.g. the second level even if it is contextualized. As a result, there is not really a difference anymore between a contextualized tree and non-contextualized one. In absence of a specific navigationDepth configuration, a contextualized tree has a default depth of 1, while a non-contextualized tree has an unlimited default depth.

• a new node type, separator, has been added. The separator node is smart enough to hide itself in case all documents between two separators would not be visible (e.g. as a result of access control restrictions).