Add a macro to render a table with selected change information for a document.

Allow to render a table of glossary items more easily. Basically the doctype is predefined and the term names may be added to the macro body.

Make the information provided in the document properties available in the HTML metadata. Allow to export the information manually (with a property control named 'export') and allow to select a set where an automatic mapping is applied.

When a property value is specified with the Confluence Date Picker, we should add artificial properties for the plain, the timestamp, and the normalized value.

The normalized value will contain a date representation to be used with Lucene as in
$[Creation Date§]: [${Last Update§} TO NOW]

Also add the normalized version for CREATION DATE and LAST MODIFICATION DATE.

Add a macro to add the names of groups with view permissions to the list of role names.

To make the rendering of the creation and modification dates more appealing we should represent them in the date picker element.

Allow wizards to transform a date value to a date picker.

Users select a date in a page wizard. The template author specifies properties to be transformed by the property 'projectdoc-adjustVarValues-toDatePicker'. All values associated with one of the specified date will be rendered as a time element that is rendered as a date picker.

To query for document instances by "Index Key" create an index key as artificial property.

The property is just the first letter of the name of the document.

It may be overridden by the author with a document property.

There are use cases where a user requires to exclude selected spaces from the closure of e.g. search spaces. In this case the user specifies "@all" and then selectively removes spaces by their name.

The feature has to be supported by the query macros (Display Table) and name list macros.

Title encodings work around the problem that the title of a Confluence page has to be unique within a space. The encodings are defined by the template author and should be activated by default. But it may make sense to allow the page author to switch it off.

In future versions we may add features to allow information architects to define the encodings as space properties.

As the tilte field is mandatory it can no longer be left empty so this usecase is no longer supported. By introducing @self this use case could be provided once more.

Allow to render sections or marked content only, if a specified property is available in this document.

This is similar to the required space properties parameter already provided by the Section Macro and the Content Marker Macro.

To define a projectdoc document the presence of the properties table should be sufficient. Currently it is required that the document has a label that matches the name of the doctype.

We need to check if queries suffer a performance impact.

Allow to define the alignment with the selected property names of the Display Table Macro.

Currently the space properties 'search-space' and 'delegate-space' are returned 'as-is'. We need to return the resolved value for these two properties (as long as they both are transitive closures).

The rendering of the iteration macro must be changed to support an easy Scroll-Office support.

Once the result set is created the information to display for each hit is determined. If the page has been removed, a warning message is written to the log.

Since this is not a warning but an information for trouble shooting, it should be set to 'DEBUG'.

Handle the strategy for rendering the link by a selection box instead of multiple exclusive checkboxes.

If the Document Properties Marker Macro delegates to a document, a property is marked as to 'delegate' (via control) and that property does not exist in the delegate document, a NPE is thrown.

The macro should be graceful with not existing properties.

Before 1.10 projectdoc relied on the 'projectdoc' label to mark pages that are projectdoc documents. We now want to remove this visible tag and replace it with a content property. The inner workings will then check the content property instead of the tag.

For migration we will always check the content property first and then the label to determine if a page is a projectdoc document. If the 'projectdoc' label is removed we will automatically add the content property.

This is a breaking change for those that expect that projectdoc documents will have a 'projectdoc' label. For instance users who use the content-by-label macro will not find new pages.

A side effect of this change is that pages with named doctypes, that is doctypes that are not based on a blueprint, will not have the name of the doctype as a label. This is - for instance - the case with the docsections.

A property value that contains a Confluence link is not recognized as having content. It should not be deemed as being empty.

If a section is rendered as a property within a cell of a table that is rendered by the Tour Macro then this content is rendered as inline. This leads to a compact rendering of e.g. lists.

On space creation the homepage is not in the Lucene index and therefore the Properties Document Marker Macro renders this error message:

Cannot find referenced document: null

Reloading the page replaces the error message with the properly rendered properties.

This also applies to Confluence pages that are converted to projectdoc documents.

The Display All Document Properties Macro cannot render content / page properties.
Instead of listing the properties, an error message is rendered.

When a new document is relocated to its doctype homepage (on creation), the document is stored at the correct location, but the ancestor information does not reflect this. The ancestor still points to the old location.

Table cells that contain two property values that are rendered as boxes are larger than the box values in cells where there is only one value.

If the render mode of the Display Table Macro is set to section style, the heading is not rendered.

The tabular style is broken. The elements following the list are flowing on the right side.

The content should be rendered below the list.

Using IE or Edge as browser the projectdoc icons in the create and create new space dialog are not displayed.