[All Adaptavist Apps]
...
The
...
{with-page}
...
macro
...
does
...
two
...
things:
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
See also the with-* macros page for an overview.
Pages can be retrieved based on:
The macro searches for pages based on these properties in the current space by default, or in any number of spaces which can be specified in the macro parameters.
If more than one search criterion is specified (e.g. labels and metadata), then only pages meeting all the selection criteria will be returned and listed by the macro (boolean AND relationship between the search criteria). Within a list of search terms (e.g. list of labels or metadata), any page matching at least one of the items in the list will be returned (boolean OR relationship within search terms).
Finally, if no page is found satisfying the selected parameters, a default page can be specified to be listed by the macro instead.
The {with-page} macro then renders the wiki markup in the macro body as if the markup were in the body of the page that was found.
Within the body of the macro, the following variables are replaced by the contents given in the following table:
Variable | Replacement |
---|---|
%withceoid% | the database id of the page |
%withceotitle% | the title of the page |
%withceoname% | the title of the page |
%withpageid% | the database id of the page |
%withpagetitle% | the title of the page |
%withpagename% | the title of the page |
This macro requires Builder 3.0 or above.
Code Block |
---|
found. h3. Retrieving a page Pages can be retrieved based on: - a specific *page name*, - page *hierarchy* (parent/child relationships), - page *labels*, and - *metadata* _keys_ or _key:value_ pairs which the pages must have. The macro searches for pages based on these properties in the current space by default, or in any number of spaces which can be specified in the macro parameters. If more than one search criterion is specified (e.g. labels and metadata), then only pages meeting _all_ the selection criteria will be returned and listed by the macro (boolean AND relationship between the search terms). Finally, if no page is found satisfying the selected parameters, a default page can be specified to be listed by the macro instead. h3. Rendering in the context of the page that was found The \{with-page} macro then renders the wiki markup in the macro body as if the markup were in the body of the page that was found. Within the body of the macro, the following variables are replaced by the contents given in the following table: || Variable || Replacement || | %withceoid% | the id of the page | | %withceotitle% | the title of the page | | %withceoname% | the title of the page | | %withpageid% | the id of the page | | %withpagetitle% | the title of the page | | %withpagename% | the title of the page | h2. Requirements This macro requires [Theme Builder 2.0|Documentation] or above. h2. Usage {code} {with-page:direction=ancestors|startPage=My Page|space=DOC|title=Page 1,Page 2|label=test,label2|metadata=key1,key2:value1,key2:value2|default=Default Page} {code} |
Examples
...
of
...
common
...
structures
...
can
...
be
...
found
...
in
...
the
...
examples
...
below.
...
Property | Required | Default | Notes |
---|---|---|---|
direction |
| The direction (in page hierarchy) that the macro should look in when searching for pages. The following values are permitted:
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
| |||
startPage | @self | The page to start the search from. The following values are permitted:
| |
---|---|---|---|
space |
| Comma-separated list of spaces to search in | |
title |
| Comma-separated list of page titles to search for | |
label |
| Comma-separated list of labels the page(s) should have | |
metadata |
| Comma-separated list of metadata key:value pairs, or metadata keys which the pages must posess. If a key:value pair is specified, then the key must have that value; if only the key is specified then any value is valid | |
default |
| Specifies a default page to use if no page was found with the previous search parameters. The following values are permitted:
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
* _children_ - search for the page to render with amongst the children of the start page * _none_ - dont search, just use the start page | ||startPage|(x)|@self|The page to start the search from. The following values are permitted: * _@self_ - the current page (default) * _@root_ - the root of the current page's tree * _@parent_ - the parent of the current page * _@home_ - the homepage of the current space * _pagetitle_ - a named page (either the page title, or spacekey:title) | ||space|(x)| | Comma-separated list of spaces to search in | ||title|(x)| | Comma-separated list of page titles to search for | ||label|(x)| | Comma-separated list of labels the page(s) should have | ||metadata|(x)| |Comma-separated list of metadata _key:value_ pairs, or metadata _keys_ which the pages must posess. If a _key:value_ pair is specified, then the _key_ must have that _value_; if only the _key_ is specified then any _value_ is valid | ||default|(x)| | Specifies a default page to use if no page was found with the previous search parameters. The following values are permitted: * _@self_ - the current page (default) * _@root_ - the root of the current page's tree * _@parent_ - the parent of the current page * _@home_ - the homepage of the current space * _pagetitle_ - a named page (either the page title, or spacekey:title) | h2. Examples h3. List ancestor pages Let's start with a simple example: listing all ancestor pages (i.e. parent, parent's parent, etc. all the way to the root of the current space). {code} List of all parent pages (from the current page) {code} Which results in: List of all parent pages (from the current page): :direction=up} As you can see, each page in the space's hierarchy, from the current up to the top (root) is listed as a link to the page itself. h3. List all children pages Similarly, we can list all children, and children's children pages from the current page, much like the \{children} macro does, but then recursively (at infinite depth): {code} List of all children pages (from the current page) down} {code Which results in: List of all children pages (from the current page): :direction=descendants} h3. Specifying the starting page for the search You may specify the page at which the \{with-page} macro should start searching. By default (if nothing is specified) this will be the current page. For instance, to list all pages in a space, specify the spacekey: as the parameter for startPage as follows: {code} List of all children pages in the [Builder|Builder:] space {with-page:direction=down|startPage=Builder:} {code} Which results in: List of all children pages in the [Builder|Builder:] space {with-page:direction=down|startPage=Builder:} h3. Searching in more than one space You can set the \{with-page} macro to search for pages in more than one space. By default, the macro will search for pages
|
Expand | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
space. You can specify different space with {{startPage=spacekey:}} as per example above. Additionally, you can specify a list of spaces to search in: {code} List of pages in the [Builder|Builder:] and [Bubbles|Bubbles:] spaces: down startPage=@home|space=Builder,Bubbles {code} Which results in: List of pages in the [Builder|Builder:] and [Bubbles|Bubbles:] spaces: startPage=@home|space=Builder,Bubbles} h3. List all pages with specific names The \ macro can retrieve pages based on their names (page titles). For this, use the following syntax: code} List of pages titled "Panel Macros", "Menu Macros", or "Utility Macros" in the [Builder|Builder:] space: { :direction=down|startPage=Builder:|title=Panel Macros,Menu Macros,Utility Macros List of pages titled "Panel Macros", "Menu Macros", or "Utility Macros" [Builder|Builder:] space: {with-page:direction=down|startPage=Builder:|title=Panel Macros,Menu Macros,Utility Macros} h3. List pages with given labels The \{with-page} macro can be used to list pages containing any one label in the list specified. Pages listed by the macro will have at least one of the labels. {code} List of pages labeled 'builder' or 'theme': builder,theme code Which results in: List of pages labeled 'builder' or 'theme': {with-page:direction=down|label=builder,theme} h3. List pages with given metadata A list of metadata _keys_, or _key:value_ pairs, can be given to
|
Expand | |||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||
as search criterion. If you specify a _key:value_ pair, then macro will return only pages containing both that _key_ and the specific _value_ for that key. If you only specify a _key_ then the macro will return all pages containing that _key_, regardless of the _value_. See the [Metadata plugin page|http://confluence.atlassian.com/display/CONFEXT/Metadata+Plugin+2] for more information on the Metadata plugin and _key:value_ pairs. List of pages authored by [~gfraser] in the [Builder|Builder:] space: down Builder: metadata=author:gfraser} {code Which results in: List of pages authored by [~gfraser] [Builder:] : with page direction=down| Builder: metadata author:gfraser h3. Specifying a default page to return In order to prevent the macro from returning an empty list in case no pages are found meeting the given search criteria, you may specify a default page to return. {code} List of parent pages: down @root default @home} {code} Which results in: List of parent pages: {with-page:direction=down|startPage=@root|default=@home} h2. CSS Customisation To follow. h2. Hints and Tips None at present. h2. Frequently Asked Questions None at
|
None at present.
None at present.