When the admin imports a space the projectdoc Toolbox starts the refresh of the space if a Build Index is requested. Since we do not render the state of this process in the administration screens, it is difficult for admins to determine whether the process has finished or not.

In addition to that we also should not automatically start a rebuild or refresh, since we do not really know what is the best move.

Therefore, we should leave the decision what to do to update the projectdoc databases to the admin. If a site is imported, a complete rebuild should be started. If only a single space is imported, then maybe only this space should be refreshed, either with the standard Space Admin Refresh or – with more control options – via a REST call.

With this removal we add a box to the Import Screen so that admins are reminded that additional steps may need to be taken. A similar reference has already been implemented on the Content Indexing screen.

We will also render messages to the log on INFO level. This may help analyzing issues by an admin or by the development team.

We consider this a breaking change albeit only an automatic refresh has been removed that may cause harm and can easily be executed manually via existing options. It is listed as a breaking change since a feature has effectively been removed and a removal is a breaking change be definition. We handle it as a bugfix version and not as a major version (according to Semantic Versioning) since we effectively removed a design issue.

When rendering properties in the TourMacro, the properties of referenced projectdoc Documents do not show up when the HTML Export is running.

It is expected that the properties can be rendered in View, PDF, and HTML Mode.

When the admin imports a space the projectdoc Toolbox starts the refresh of the space if a Build Index is requested. Since we do not render the state of this process in the administration screens, it is difficult for admins to determine whether the process has finished or not.

In addition to that we also should not automatically start a rebuild or refresh, since we do not really know what is the best move.

Therefore, we should leave the decision what to do to update the projectdoc databases to the admin. If a site is imported, a complete rebuild should be started. If only a single space is imported, then maybe only this space should be refreshed, either with the standard Space Admin Refresh or – with more control options – via a REST call.

With this removal we add a box to the Import Screen so that admins are reminded that additional steps may need to be taken. A similar reference has already been implemented on the Content Indexing screen.

We will also render messages to the log on INFO level. This may help analyzing issues by an admin or by the development team.

We consider this a breaking change albeit only an automatic refresh has been removed that may cause harm and can easily be executed manually via existing options. It is listed as a breaking change since a feature has effectively been removed and a removal is a breaking change be definition. We handle it as a bugfix version and not as a major version (according to Semantic Versioning) since we effectively removed a design issue.

In some use cases a warn message is logged if a task has not a unique key to identify.

All tasks have names, but this seems not to be sufficient for some use cases. Therefore, we need to override the base method of our task implementations to provide a unique key.

Content Macros that do not render if user has no write access to the page the macro is part of, should also not render if the macro is rendered in export mode.

Export mode includes HTML and PDF Export.