The space property console must support to have the delegate-space and search-space property to be defined in a space properties extension.

This is required for space publishing to define space configuration properties on an extension page that is actually not published.

Although there is no hint in the release notes the generation of the HTML identifier seems to have changed. While prior to version 7.4 the identifier contained the dashes ('-') of the page title, the version 7.4 removes them.

The fix is required for intra-page links to sections and for resolving intra-page links (for instance in transclusions).

Allow to flag content marker and sections to be considered to be empty content. This way content or sections may not be shown if only such marked content or other empty content is provided.

We need to add the feature of being remote controlling to more macros than the Wiki Link Macro.

Included are the Display Table Macro, the Transclusion Macro, and all of their siblings and cousins.

Allow users to define materializers by space properties (projectdoc-materialize-(doctype)).

The artificial properties URL and Tiny URL need to be redefined.

The property should provide a link in HTML, the text form (e.g. URL$) should contain the label (which is the name of the document), and only the normalized form (e.g. URL§) should contain the plain URL string.

This may break code where users fetch the URL property and expect the plain URL but get HTML. This can be fixed by fetching URL§.

Since the three properties provide the same value, this is considered a bug.

We want to render section macros and content tables in case the projectdoc Toolbox is running without license. This allows users to still read their content in the rendered page. Otherwise the content would only be available in the storage format.

The macros will render their content, including their parameter values, but will not execute their code.

Provide two more values for the Discard parameter:

1. full: Filter on table rows where all cells have content
2. partial: Filter on table rows where at lease one cell has no content

Provide form parameter projectdoc-adjustVarValues-toVersion to provide an expanded version to the page creation process.

The services need to provided means to change the document property controls via the REST API.

The Cite Macro should render the short description of the referenced document per default. It may be overridden with a static string.

For Display Document Property Macros we need to allow the selection of an unknown property name. This is especially important in case of a new document. We have no access to the draft currently, so we need to allow the user to specify an arbitrary property name.

A use case may also be to specify a property that actually does not exist, but may exist in the future. Typically we would suggest that such a property exists in the doctype with an empty value, but this is not necessarily the case. Especially for users that do not work with doctypes.

Allow that the Wiki Link Macro refers to the page it is part of.

The macro references its page if the document and page parameter are empty or if the the document or page parameter is set to @self.

Links to self can be used for remote control.

To make it easier for users to reference the same document for transclusion, we allow the empty document to refer to self.

To prevent unintended transclusions on the very same document because of carelessness we demand that either the document, ids, or tags are specified. The document may have its title or the placeholder @self as value.

To calculate the doctype of the documents hosted by a doctype homepage, the service solely relies on the naming convention of an I18N key. Users who do not provide their doctypes in form of doctype add-ons cannot use this feature currently.

We therefore need an additional check to determine the doctype by looking at the Flags property of the doctype homepage. 

projectdoc.doctype-home, projectdoc.all, projectdoc.related.doctype.<doctype>

If the values above are present for the Flags property, the doctype is derived from the third property above (the property values may be specified in any order).

Transcluding transcluded content using the Transclude Documents Macro renders the level on "1" when target level blank is selected. It should be adjusted as it is when the level is set to '*'.

We need a special treatment for the Jira Macro as a value in the properties table. Otherwise the rendered content is displayed differently for different users.

We need to check if we need a new property control and if we could detect the use of the Jira Macro to automatically select the property control.

The Transclusion-to-Text Macro fails to properly parse the body when called from a context where the macro version is used in wiki-syntax (curly version). The context provides the body of the macro not as plain text, but with HTML markup.

The macro expects replacements separated by newlines. In case the body is presented with HTML elements, the replacements cannot be resolved properly.

Currently we select the increment specification by the doctype of the identified document, but must use the doctype of the parent document.

The doctype needs to be calulcated in higher priority than artificial properties.

Currently the doctype "default" is rendered instead of "tag"

<span class="projectdoc-document-type-default projectdoc-namelist">Test Tag</span>

Check the Role Name Macro.

Also check if we should provided data-attributes in addition to the CSS selectors.

Add a row counter to keep track of rows more easily.

The service allows to fetch and override Auto ID information for a given page.

The Wiki Link Macro should set projectdoc-doctype-<doctypeID> as a selector to the CSS attribute of the anchor element for the generated link.

Entering a blank value should override the tooltip for the Wiki Link Macro.

The Transclusion-to-Text Macro does not support Autocomplete for the IDs and Tags parameter.

Although the macro is deactivated per default, when activated the autocomplete feature should be supported.

The additional information would make it more obvious to users how the macro is configured when in page edit mode.

Macro preview with macro content is not supported and should be shown as message.

Define the I18N key projectdoc.doctype.common.duration.delimiter to specify a delimiter between the start and end of a duration.

When fetching a value to create the space closure (for search and delegate spaces), a space may prevent calulating the correct value. This is especially the case if the space is a nbsp.

The artificial property value for the doctype homepage URL contains a redundant slash.

When parsing the normalized URL (artificial property) the original value is expected to be a valid HTML fragment, but it is a plain text. Therefore parsing this value fails.

The artificial document property Tiny URL et al. must not be considered as a User Space Property.

• IDENTIFIER
• ID_PREFIX
• DOCSUBTYPE
• IS_A
• IS_OF
• IN_CONTEXT
• DIRECT_ANCESTOR_ID
• DIRECT_ANCESTOR_TITLE
• ANCESTOR_TYPE_NAMES
• ANCESTOR_IDS
• ANCESTOR_NAMES
• ANCESTOR_TYPE_IDS
• ANCESTOR_TYPE_NAMES_SUFFIX
• ASPECTS
• AUTHORS_OF_QUOTES
• LATEST_VERSION_COMMENT_WITH_COMMENT
• LATEST_VERSION_COMMENT
• LATEST_VERSION_NUMBER_WITH_COMMENT
• VERSION_HISTORY
• CONTINUATION_OF
• DELEGATE_DOCUMENT
• DELEGATE_DOCUMENT_DOCTYPE
• DELEGATE_DOCUMENT_IN_CONTEXT
• DELEGATE_DOCUMENT_IS_A
• DELEGATE_DOCUMENT_PAGE_LINK
• DELEGATE_DOCUMENT_PAGE_REF

When merging definition lists with the Table Merger Macro, identical definition data elements are filtered, but should not. 

Also definition data must not be shown if the definition term has been rejected as duplicate.