Skip to main content
Skip table of contents

Known Issues

Note: If you have updated from version 7.0 to version 8.0, the page Migration to Version 8 contains a troubleshooting chapter that might be of use.

Issue when using default values/placeholders in template root pages


When using default placeholder or placeholders that have default values (See Default Value Macro (PRO)) in page titles, the Page Tree Creator will replace these placeholders with the actual value during evaluation of page references configured in the Page Tree Creator Create Space and Create Pages Macro.

This behavior is desired in some cases, see Exclude Content Macro (PRO) for more details

However in the following scenario this might lead to unexpected behavior:

  • The Page Tree Creator Button’s source page and target page are located in the same space

  • The source page’s page title contains default placeholders or placeholders with a default value

  • There already exists a page with the same page title as when replacing the placeholders in the source page’s page title

In this case, the Page Tree Creator will not copy the configured source page but the other page.

Example and Solution


To reproduce the error, make the following page structure:

  • Root Page

    • __current_date__ - My Template

  • Set a Page Tree Creator Button on the Root Page with the source page “__current_date__ - My Template” and target page empty (points at the Root Page itself)

  • Add a placeholder to the source page's content, e.g. “__placeholder__”

When using the button first, you will be presented with a ‘placeholder replace’ dialog, where you can enter a value like “Test Replacement” for the “__placeholder__” resulting in the following structure:

  • Root Page

    • __current_date__ - My Template

    • 01.01.2021 - My Template

The content of the newly created page will be “Test Replacement”.

When using the Page Tree Creator Button a second time, you will see, that the ‘placeholder replace’ wizard page will be skipped and when creating the page and that the page content will also be “Test Replacement”. This happens because the Page Tree Creator didn’t create a new page based on the template page, but it evaluated the default placeholder first and used the “01.01.2021 - My Template” page as template.

(If executed on the same date)

The same behavior can be observed for any default placeholders


There exist two independent solutions to prevent this unexpected behavior:

  1. Keep your templates in a separate template space

  2. Add a template sticker to your templates

Just set a Template Marker in the front of your template root page

Per default this marker is _Template

It can be that your confluence administrator has changed this

“__current_date__ - My Template” becomes “_Template __current_date__ - My Template”

Error loading Templates when updating Confluence


Confluence version was updated for example to Confluence version 7.13.7 and now there is an error message when trying to create from templates.

Error message | Image


Atlassian removed some dependencies because of vulnerabilities and we updated those dependencies in Page Tree Creator version 8.4.1 → Update the Page Tree Creator to version 8.4.1 or newer.

The PTC Template Macro is missing on my template


The following instructions also work for other Macros like PTC Template Page macro and STC Tag Description Macro.

This is a problem in relation to the Collaborative editing feature.

No Template Macro on the template page | Image


Step 1: Revert draft

Open the page in Edit mode and select Revert to last published version on the bottom right.

Step 2: Check for changes

In the opened dialog click on show changes. There should be some changes regarding the PTC Template Macro.

Changes can be displayed very different when for example something is changed in a table.

Step 3: Click Revert page

After inspecting the changes and writing down important changes click on revert page.

Important changes can be applied afterward again.

Now there should be the PTC Template Macro on the page.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.