The following properties are mandatory to appear in the document properties table:

• Doctype - must be plain text
• Name - optional if Nameless Documents are in use (note that space homepages cannot be nameless)
• Short Description - optional if no overviews e.g. using the Display Table Macro using default selection is used

Especially a missing Doctype property – since version 2.4 also if the macro contains no table – is reported immediately as an error.

This error is also rendered if the language of the site differs from the language defined for the user. Please make sure that the browser's language (or locale) matches that of Confluence (users with write permission typically experience no trouble if their profile has the correct language set). See Language Problem below.

Each page is created based on the site language (more specific: the site locale). If the site language differs from that of the page, the macro is not able to find any document properties.

The language for the whole site can only be configured by an admin.

This problem occurs usually, if a space is imported from a site based on a different language. There is no workaround for this problem than translating the pages. This is a problem - to our knowledge - that is shared by all macros that display generated text resources.

If a document has already been created with the wrong language, all property names and sections need to be replaced (for instance the macro is looking for 'Dokumenttyp' since the language is set to German, but the property in the document reads 'Doctype'). This is because a page in Confluence has no reference to the blueprint it has been created with. Often it is easier to create a new page with the blueprint wizard and copy the property values and section bodies from the old to the new document.

Please note that there must only be one instance of this macro on a page.

This macro is the working horse of projectdoc. It provides the basic information to transform a Confluence page into a projectdoc document. This allows users to employ automatic lists to display documents by their metadata.

Since version 1.11 authors may render groups of properties with the use of one or more instances of the Document Properties Supplier Macro.

Since version 1.15 authors may include properties from attachment files with the use of one or more instances of the Document Properties Supplier Attachment Macro.