Export Whiteboard Not Supported PDF issue

[Anastasiia Roshchupkina]

We have a section as a folder in the confluence, and after exporting it to the PDF, we get an empty page with the folder name and the message: export.whiteboard.not.supported

The inner content starts from a new page. How can I fix that and avoid page breaks? Thanks 

[Humashankar VJ]

@Anastasiia Roshchupkina 

Also am looking into the concerns about the Table of Contents title and the page break issue. Let me get back to you on that in sometime

[Humashankar VJ]

Hi @Anastasiia Roshchupkina 

Ensure that you're exporting the entire whiteboard and not just a selected area, to learn more - Export your whiteboard | Confluence Cloud | Atlassian Support

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

[Anastasiia Roshchupkina]

Hi @Huma 

Thank you for the reply. But can not understand where I can find it. I see this in the PDF download section:

Is it possible to fix such things in the PDF stylesheet? Thank you.

[Humashankar VJ]

Hi @Anastasiia Roshchupkina 

I understand your concern regarding the issue with exporting Whiteboards to PDF using the PDF stylesheet. Unfortunately, this limitation cannot be resolved through the stylesheet alone.

• The "export.whiteboard.not.supported" message you're encountering is a known constraint of Confluence's PDF export feature, which currently doesn't support direct PDF export of Whiteboards. 
• For customization options, you can access the PDF stylesheet in two locations: Administration > General Configuration > PDF Stylesheet for global changes, or Space Tools > Look and Feel > PDF Stylesheet for space-specific adjustments.

While the stylesheet allows customization of various PDF export aspects, such as fonts and page breaks, it cannot enable export functionality for unsupported elements like Whiteboards.

Customize Exports to PDF | Confluence Data Center 9.1 | Atlassian Documentation

Best Regards

[Anastasiia Roshchupkina]

Hi @Humashankar VJ 

Thanks, I just checked one thing regarding the CSS and if I put this style:

.pagetitle
{
page-break-before: auto;

}

this message disappears, but due to this property, all headings are without page breaks. However, I need the page break for the h1 pageTitle.

Maybe you can also help me with the bullets, please - https://community.atlassian.com/t5/Confluence-questions/PDF-Bullet-list-export-issue/qaq-p/2869219#M327414?

And also, have another issue - when I try to add the Table of Content title like here https://confluence.atlassian.com/doc/customize-exports-to-pdf-190480945.html 

<div class="fsTitlePage">  
 <img src="/download/attachments/169118009/atlassian_logo.png" />  
<div class="fsDocTitle">Documentation for Confluence</div>  
</div>   
<div class="tocTitle">Contents</div>

It appears but has a page break before the content. Is there a way to fix it? Sorry, so many questions :) Thank you

[Humashankar VJ]

@Anastasiia Roshchupkina 

Thank you for providing additional context! I understand you're trying to balance page breaks for different heading levels in your PDF export from Confluence. Here's how you can adjust the CSS to meet your needs:

To Keep Page Breaks for H1 (PageTitle) Only:

css

Copy code

.pagetitle {

  page-break-before: always;

}

h2, h3, h4, h5, h6 {

  page-break-before: auto;

}

This ensures that h1 (pageTitle) starts on a new page, while other heading levels (h2-h6) do not force page breaks.

To Preserve Bullet Lists in PDF Exports,

css

Copy code

ul {

  list-style-type: disc;

  padding-left: 20px;

}

ul li {

  display: list-item;

}

ul li::before {

  content: none;

}

Above CSS Covers the below technicals,

• Sets the list style to disc (bullet points), Adds left padding to the list
• Ensures list items are displayed correctly and removes any custom content that might be interfering with the bullets

You can add both of these CSS snippets to your PDF stylesheet in Confluence. To access the PDF stylesheet:

• Go to Space Settings > PDF Export > PDF Stylesheet, "Edit" and Add the CSS snippets

After implementing these modifications, attempt to export your content to PDF once more. You should now see the following improvements, the page title (h1) will start on a new page, other headings will no longer force page breaks, and bullet lists will display correctly.

[Anastasiia Roshchupkina]

Hi @Humashankar VJ 

Thank you for your help, but, unfortunately, it doesn`t work :( The bullets are still the same: 

The heading styles are working, thanks, but, unfortunately, the folder title and a section title both have the pagetitle class and the first one (folder title) appears on a separate page. Maybe there is a difference between h1.pagetitle classes? Thank you

[Humashankar VJ]

@Anastasiia Roshchupkina 

Confluence's handling of h1.pagetitle classes during PDF exports exhibits distinct behaviors. Especially, page titles are rendered as h1 elements with the pagetitle class, while heading levels within the content are adjusted. Specifically, the first h1 in the content becomes an h2, and subsequent headings are demoted accordingly to maintain a logical hierarchy.

Moreover, Confluence does not provide a built-in method to differentiate between parent and child pages using CSS selectors alone. All page titles, regardless of their hierarchy level, share the same pagetitle class and structure. This limitation makes it challenging to distinguish between page levels in the left-hand navigation menu.