On an existing Wiki page, the page tree allows me to expand pages that contain child pages e.g.
when I click the rightarrow next to "General Information", I see the child pages.
However, in another space, I do not see the rightarrow next to "expandable" pages.
How to activate?
The sidebar is not controlled by the content of the page. It depends on the theme that is selected for a space (some themes don't have that sidebar at all). If both of your pages are in the same space, then the sidebar should look the same - it will just unwrap to show you the position of the page that you are currently looking at.
If you're working in different spaces, then there is a chance that your sidebar settings are different, or the theme is.
More on that here:
Hmmm... it may be a bug, but I can't reproduce it.
Try to open the page and see if the page tree macro has been configured properly (double click on the macro to edit its attributes). Make sure that it uses proper root page, and so on. If nothing helps, report an issue to Atlassian.
OK you may be on to something.
For the page that works correctly, the sidebar contains the header Page Tree.
For the page that does not work correctly, the sidebar contains the header Child Pages.
Both pages have a Children Display macro, not a Page Tree macro. As far as I can tell, both macros have teh same setting.
What do I look for next? The underlying issue must be the related to Page Tree vs. Child Pages.
Ah, that explains everything . Children display macro by default shows you only the immediate children of the page - without the option to drill down. If you want that drill down feature, you need to edit the page and replace the Children display macro with the page tree macro.
More about the macros here:
Children display: https://confluence.atlassian.com/doc/children-display-macro-139501.html
Yes, that's what I thought, too. However, the screenshot below shows that the "page that works" also contains the Children Display Macro, not Page Properties.
Interestingly, though, this page used to contain a Page Properties macro before someone changed to Children Display
Does any of the above make sense? Thanks!
children display doesn't provide that drill down capability, so unless this is coming from an excerpt (included content from a child page), I'm not sure why you see that arrow.
Still, I would go ahead and replace that with the page tree and that should do the trick.
OK, forgive my confusion...I'm still relatively new to Confluence.
When I stated that the "page that works" previously contained a "Page Tree" macro, I meant "Page Properties Report". I do not recall seeing a Page Tree macro in that page; then again I've worked for the client less than three months and it's possible it previously existed.
In any event, I added the page tree macro, but it did not do what I needed.
Oh yes! That solution worked! I changed from Child Pages to Page Tree.
All is good. I think this whole exercise proves that the best way to learn an application is to use it!
How do I convert your last comment to an answer?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Atlassian market place contains number of Apps/Addons which improves the capability of out of the box Atlassian products. It is good to follow a plugin evaluation process before install add-ons. So t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs