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.
Example Box |
---|
title | Example Configuration for German (Deutsch) |
---|
| Note that this has nothing to do with the Indexing Language of General Configuration. This is typically not changed from its original value (which is English even if the global default language is set to another value).
|
Info Box |
---|
This is really only relevant for properties that have meaning to the system. Only in this case the system has to translate the name of the property. Other properties are usually passed through without translation. Therefore users may add any number of properties without the need of providing localization bundles (these are resources that contain text for a specific language). |
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. Info Box |
---|
A page in Confluence containing generated text will contain this text regardless of any changes of the language after creation. This is similar to any user added text. The user (without the help of third-party plugins) writes text to a page in one language. |
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. |