To be DC compliant the projectdoc Toolbox needs to put an upper limit to the result set. This is to be a configuration option in the administration screen and defaults to a value of 100.

In case the result set is actually larger than 100 hits, the macros need to render a box with a warn message. Users should then put additional constraints on their queries.

It may make sense to provide paging in a future version of the projectdoc Toolbox. Since the design goal is to be printable, the paging would only be an alternative representation of the warning box. There will be no alternative view for PDF export where the query renders more than the specified maximum of hits, since this would violate the DC requirements.

Required to remove load from the async events to update documents when stale information has been encountered on read.

Check all parameters for characters that may harm the log file. Currently we sanitize the parameters before logging, but we need to make sure that the log is not manipulated after the first check. Therefore we now reject all requests where harmful characters are contained in request parameters. 

The script that renders the chrome for macros to be expanded fails in some use cases. Then the chrome of the macro (especially the title of the section macros) is no longer visible.

A workaround in some use cases is to revert the page. This removes all changes to the draft, but the macros are rendered correctly.

When the doctype cache is cleared, then not all service runs detect that the whole cache is to be restored. Some use cases only add the doctype information that has been requested with a cache miss.

The workaround is to clear the doctype cache manually.

If a property value contains a comma, which is the default separator for list items, then a user may take advantage of the is-single-value control to specify that this value is required to be taken as a single value.

The user has not this control over artificial properties, like the Title.

We need to make the Title and the identifying artificial properties single values per default. This includes, for instance, projectdoc.doctype.common.name, but not Name. For Name the user has control over how to interpret the value and we do not want to interfere with existing use cases.

Allow to configure the system to prevent the use of dynamic macros as property values.

If a dynamic macro is used as a property value, an error message will be rendered on that page and the incident is logged to the health logger.

When rendering the PDF version of a page, the rendering of the box icons fails in some contexts. No icon is rendered.

When printing the intra-document links are not always rendered properly. The print-quirk-mode named suppress-in-document-links should allow to suppress the rendering of this links (currently only supported by the In-Document Link Macro).

The Table Merger Macro fails to merge definition lists in case the root of the list is not top level even if marked with the class selector.

In case the selector is used, for instance with the Tour Macro, the Table Merger Macro must be able to do the merge.

The section heading on the separate pages fails to start with the correct level. Instead the level 1 always starts with 0.

Currently only pages are considered to be projectdoc documents. In case of a blog post, we need to reject the parsing of the abstract page.

When the macro context is created outside a conversion context (i.e. not in a context where a macro is run), then a NPE is rendered.

The context must be detected ant the NPE prevented.

The text

"During the rebuild the site should be in read-only mode and is probably not usable. Note that the projectdoc Toolbox provides REST services to run the process on sets of spaces."

is not correct.

For one, it is not the site that is not usable, but the spaces with projectdoc documents that have not already been rebuilt.

Second, it is not possible to do an upgrade or an rebuild on single spaces. These two modes can only be run on a site. The documentation of the REST services address this correctly.

The text should read:

"During the rebuild the spaces with projectdoc documents are probably not usable. Consider to set them read-only. The process may complete quicker, if every space with projectdoc documents has a projectdoc homepage."

We should also render the link to the manual in the projectdoc Refresh section.

There are a couple of typos and character issues in the resource bundle for DE.

In case a projectdoc document is accessed on the login page, then the document cache should be provided. Since we are using an allow list here, we need to add the login page.

Instead of fetching the property values from fetched documents, the values can now be directly fetched from the Lucene result set.

This applies only for the Name List Macro and only in use cases where it is allowed by the configuration (de.smartics.projectdoc.name-list.use-short-circuit-result-sets=true) and the template parameter is not used.