Header and footer implied variables differences between cloud and server

Mark Kobold June 14, 2021

While migrating Confluence from server to cloud. The page tree macro was used in the Confluence global header and footer for all pages and spaces. 

The wiki markup in the foooter was as follows:

`{pagetree:root=@self|sort=natural|excerpt=false|reverse=false|startDepth=1|expandCollapseAll=false|searchBox=false}`

Yields the following error message when the Confluence page is rendered

The root page <space-key>:@self could not be found in space <space-name>. Similar threads on this error message imply that this is because the home page for the space is not set. I have confirmed that it is and the issue still persists. 

Also using the space specific footer versus the global/system one yields no effect. I have also tried in different Confluence Cloud instances to rule out any potential weirdness there.

If the same wiki markup text is put into the actual page in Confluence it works as expected. So the macro structure and configuration is believed to be correct and accurate. 

From the looks of things this feels like a bug in Confluence that when the headers and footers are rendered for each page. They are done so in a different context than the page itself. Which would explain why the macro wouldn't necessarily resolve the @self parameter properly. Though it does seem to be aware of the space it is in.

Could someone confirm or deny this? Thanks in advance.

1 answer

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 24, 2021

@Mark Kobold , did you ever get this resolved? If not did you reach out to Atlassian Support?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events