-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
6.14.1
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
Space export as PDF doesn't handle page hierarchy correctly.
It seemed to work correctly on Confluence 6.6.4 at least.
Steps to Reproduce
- Create pages with the following hierarchy in a space
- 1 first level -- 1.1 second level --- 1.1.1 third level
- Export the space as PDF
Expected Results
- Each page title should be shown with appropriate style based on the hierarchy like
- Each page should e shown without any page break
Please refer to 6.6.4.pdf
which was exported from Confluence 6.6.4.
Actual Results
- Each page title is shown with the same style
- There are page breaks between the pages
Please refer to 6.14.1.pdf which was exported from Confluence 6.14.1.
Workaround
No workaround was founded.
[CONFSERVER-57998] Space export as PDF doesn't handle page hierarchy correctly
Chikara Takahashi
added a comment - Hello, I would need same appearance what Okamoto-san is requesting. I liked the appearance until 6.12... I would need workaround to do same as 6.12 in 6.13.
Chikara Takahashi
added a comment - Hello, I would need same appearance what Okamoto-san is requesting. I liked the appearance until 6.12... I would need workaround to do same as 6.12 in 6.13. Hi yokamoto!
As listed in the release notes, each page PDF is generated separately and therefore we do not inherently provide a way to identify child pages by their heading level.
With that said, headings are not rendered uniformly (i.e. if two pages contain a h5 element, the rendered heading will look the same no matter the hierarchy) - so to achieve this effect one of the only solutions is to actually change the heading sizes on the child pages (or use something like the HTML macro, which we tend to discourage).
| Resolution | New: Not a bug [ 12 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
This is an intentional change introduced in Confluence 6.13 to allow customers to apply their own styles to headings.
Please refer to the Confluence 6.13 release notes here.
This article gives a in-depth overview of how you can customise PDF space exports.
| Assignee | New: Mark Bereznitsky [ mbereznitsky ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
Space export as PDF doesn't handle page hierarchy correctly. It seemed to work correctly on Confluence 6.6.4 at least. h3. Steps to Reproduce # Create pages with the following hierarchy in a space {code} - 1 first level -- 1.1 second level --- 1.1.1 third level {code} # Export the space as PDF h3. Expected Results # Each page title should be shown with appropriate style based on the hierarchy like {panel} h1. 1 first level h2. 1.1 second level h3. 1.1.1 third level {panel} # Each page should e shown without any page break Please refer to which was exported from Confluence 6.6.4. h3. Actual Results # Each page title is shown with the same style # There are page breaks between the pages h3. Workaround No workaround was founded. |
New:
h3. Issue Summary
Space export as PDF doesn't handle page hierarchy correctly. It seemed to work correctly on Confluence 6.6.4 at least. h3. Steps to Reproduce # Create pages with the following hierarchy in a space {code} - 1 first level -- 1.1 second level --- 1.1.1 third level {code} # Export the space as PDF h3. Expected Results # Each page title should be shown with appropriate style based on the hierarchy like {panel} h1. 1 first level h2. 1.1 second level h3. 1.1.1 third level {panel} # Each page should e shown without any page break Please refer to [^6.6.4.pdf] which was exported from Confluence 6.6.4. h3. Actual Results # Each page title is shown with the same style # There are page breaks between the pages Please refer to [^6.14.1.pdf] which was exported from Confluence 6.14.1. h3. Workaround No workaround was founded. |
| Attachment | New: 6.14.1.pdf [ 342948 ] |
| Attachment | New: 6.6.4.pdf [ 342947 ] |
this may not be a bug but it should have been implemented to be backwards compatible so that companies that have been producing customer documentation like this for 15 years and paying Atlassian are not negatively impacted.. You have a check box for "add page numbers" but didn't think to add one "Auto demote headers"? I guess it will be one more plugin I have to develop. Atlassian sure does promote job security fixing all the things they "fix".