Children Display does not show all children with h1 formatting

Question

I'm using the Children Display macro and child pages will show up if I keep the output unformatted, but some of the children are not showing up if I apply any formatting options (e.g. h1 or h2).

Is this a workaround that can get all children to display?

roman_l0djep · Answer

Hi @Christine Lieu, thanks for creating a support ticket with us.

I will paste my answer from there here in case others come across this issue in versioned spaces.

In versioned spaces we replace the default Children Display macro with the one we developed to support the structure of versioned pages. The bug is within our implementation of the macro: https://k15t.jira.com/browse/VSN-4294. Sign up for an account in our Jira to watch and vote for this issue. There is currently no time frame I could share for fixing this issue, but I will mention it on the next sprint planning meeting.

If you have other questions, please let me know.

Roman.

Christine Lieu · Answer

Thanks for that info! Unfortunately, making the page un-versioned did not help with the issue. Would appreciate any other workarounds if you have ideas... I will also submit a ticket to k15t.

Stephen Sifers · Answer

Hello Christine,

We've been reviewing your screenshots of the issue along with reviewed your issue that you face. We tested the problem and found a way to recreate the issue. We did find that within a default (no add-on instance of Confluence this did not exist) instance this is not an issue. What you’re seeing is an effect of an add-on your using named Scroll Version. Within your screenshot is show that you have versions enabled within this space or pages. When versions are enabled and you adjust the header to H1 within the children display macro then any content that is version controlled will not be displayed.

A workaround for this would be to un-version the content to have it displayed under the H1 header. With this said, the issue looks to be how Scroll Version is handling the pages and headers. We found this only happened with pages that are versioned.

Examples:

Unversioned page:

Versioned:

At this point, we would suggest presenting this case to K15t to have them review as this looks to be an app issue. Please submit a case with K15t at https://k15t.zendesk.com/hc/en-us/requests/new, when creating the case reference this community post as well to show steps you’ve already taken.

Thank you for presenting this issue and working with us to help find the problem.

Regards,
Stephen Sifers