-
Bug
-
Resolution: Timed out
-
Low
-
8
-
Minor
-
1
-
Issue Summary
- When using the Page tree Macro in the new Editor, if we configure the macro with root as @self and without any search and the child page titles with the same length, when published, a new line is added.
- Macro wraps based on the longest entry, but even when the title is short (with search and no search configuration).
- Bullet point located on the top of the page tree results.
Steps to Reproduce
- Add the Page tree macro, with Search & without Search.
- Set root as @self
- Add the child pages with the same title
- Add the child pages with longer titles
Expected Results
- Page tree macro results are displayed correctly
Actual Results
- A new line when all child pages have same title length
- Macro wraps based on the longest entry, but even when the title is short (with search and no search)
Workaround
Can use Content by Label macro to list all the child pages, by adding the same label.
Also, switching the layout to wide should stop this behavior.
- duplicates
-
CONFCLOUD-65904 Allow Page Tree Macro to display items in a single line
- Closed
-
- Closed
[CONFCLOUD-68691] Page tree macro CSS problem
Is there any update or fix here? This seems to be happening for all page trees used in the new editor still.
This seems to be a simple CSS issue and the workarounds do not offer equal functionality. This really needs to be fixed.
To add weight to Andrew's comment above, the Children Display macro does not provide the Search Box option that is available (and so useful!) with the Page Tree macro...
Please fix this (yet another) silly-ism of the new editor ASAP.
"Children Display Macro as a Workaround" is a poor alternative. It does not allow 'expand/collapse' so quickly results in a long and unwieldy list if children are displayed, and if children are not displayed one loses the utility of quickly peeking into sub-pages without having to expand the left-hand navigation pane.
I had only just (about 6 months ago) gone through my site and replaced all "Children Display" macros with "**Page Tree" macros to get the benefit of expanding to view sub-pages_._ The thought of reversing this for what one would assume is a fairly minor fix is very unappealing.
You can use the Children Display Macro as a Workaround (thanks @Vikram_Chhabra see comment in community thread). This Information should be added to the 'Workaround' Section above!
http://example.com/ https://community.atlassian.com/t5/Confluence-questions/Increase-the-width-of-the-pagetree-macro/qaq-p/1083077
Long Term Back-lock? low priority?
This bug makes the macro unusable.
"Trees exhale for us so that we can inhale them to stay alive. Can we ever forget that? Let us love trees with every breath we take until we perish."
― Munia Khan
pls fix this
Priority low?
For a product that sells itself on "organise work" to not have a working table of content macro (anymore...) is unprofessional.
This whole "New Experience" has been mostly comprised of "why does this and that no longer work" rather than "uuh, this is a good, useable change".
Same issue - Page Tree Macro. I use this macro frequently and it's making page navigation difficult.
I am also having this same issue. Any update on this? It seems like a simple patch on your side Atlassian.... 
It really would make the pages so much nicer looking
It looks like if a style of 'width:100%' was added to the root <span> then it fixes the issue. Maybe a checkbox could be added to the 'Editing' panel for "Force maximum width when displaying" (I'm not good at writing descriptions).
Seems like an easy fix, I'd like to see this. It would make existing Confluence assets much easier to navigate.
I thought I was experiencing the same issue. It does not look great when we are doing presentations.
I too like to use this macro on nearly every page. Now it's just an ugly mess. Please fix!
we use this feature on almost every page that has sub-pages, and it's a complete and utter mess currently. This should be a quick fix.
Is Atlassian using the same version of confluence cloud? How can they prioritize this issue to Low? It is quite old and issue and really awful.
Please see a much larger number of affected people here https://community.atlassian.com/t5/Confluence-questions/Increase-the-width-of-the-pagetree-macro/qaq-p/1083077
For sure this bug do not have a Low priority. You should increase this BUG to HIGH priority!
BTW even font size is too low at this macro, should have the same font size like Contentbylabel macro!
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!