Yes this is still an issue, however the workaround above works - even if it indents the page heading a bit.

Hi everyone,

Thank you for previously raising this bug and bringing it to our attention.

This should be fixed with the recent changes we've made. If you feel like this bug is still impacting your team please let us know.

Thank you again for providing valuable feedback!

+1 vote to this issue! Very frustrating that such a simple thing has been left uncorrected for so long.

Lissa Meade,

Thank you for this workaround, and for hopefully saving some time to get this issue resolved by Atlassian!

Darryl

Greeting! I have just run into this issue and have been able to define what is happening to me, and the workaround I have developed. It looks like the ticket itself is out of date. I went ahead and rewrote it. I hope this helps everyone!

Summary

When both a Multi-Column Page Layout and a Single Column Page Layout is in use on a page, exporting the page to PDF cuts off the left-hand side of the content in the Single Column Page Layout.

Environment

• Confluence Cloud

Steps to Reproduce

1. Create a new Confluence page.
2. Add text into the page
3. Select the Page Layout Icon, which adds a new Multi-Column Layout section to the page
4. Add text into the cells of the new multi-layout section.
5. Publish the page.
6. Click . . . > Export to PDF

Expected Results

• The PDF file generated is normal and all text is legible. 
  • https://drive.google.com/drive/folders/1T81ccxgsbwixt70OrzZNvEcsFrQF4zd1?usp=sharing

Actual Results

• The PDF file generated is truncated on the left.
  • https://drive.google.com/drive/folders/1npIwgQkYs8iRtoBYr0oOb8YkAbINMEks?usp=sharing
• Bonus: If tables are in use, the right border of the table is cut off.

Issue Identification / Cause

Compare the "View Source" screens of a page with no added multi-column layouts vs a page that has both single and multi-column layouts in use.

The page using only a single column page layout shows that the copy is 100% wide, with no visible container.

The page using both a single column layout and a multi-column layouts in use shows that the different layout sections are encompassed by visible containers, and the width of the two layout containers are not both 100% wide; instead, the Single-Column Page Layout has a max width of 700px. 

https://drive.google.com/drive/folders/1JFgS30uBXVV-YhHqmVs47psLzOIFPcJL?usp=sharing

Although the single column page layout is shown as centered on the View Source screen, the default stylesheet for the exported PDF produces the single column layout as right aligned. The width of the container is fixed to be wider than can fit within the parameters of the PDF. The result is that the overflow does not appear on the PDF.

Workaround

Add the following to either the Space or System Default PDF Export Stylesheet:

div.wiki-content {  width: 150mm !important;  align-self: center !important;  margin: 18px !important;  }  

One of the workarounds doesn't work.

"Use another page layout instead, such as Full Width, or two or 3 columns."

We use macros with two columns and get the same problem JST-541329

Please, fix this bug, because we can't deliver documents for our customers.

I experience this issue using Full Width page layout, contrary to the workaround directions.  The UI for switching between fixed width and full width have changed at this point. 

Thanks @sostopchuck, this sorted it for me too, and doesn't break full-width exports either.

If you want all pages to have a shorter column width in the PDF (more readable), I've used:

@page {
 size: 210mm 297mm; /* A4, change for US letter */
 margin: 18mm 20mm;
}
div.wiki-content {
 width: 150mm !important;
 align-self: center !important;
 margin: 20px 30mm 20px 20px !important;
 line-height: 1.4 !important
}

(this can probably be adapted to use classes and keep full-width content at full width if needed)

If it's of help to anyone, the below PDF Stylesheet CSS is fixing the issue for me:

(Space settings -> Look and Feel -> PDF Stylesheet)

@page

div.wiki-content

Happy birthday CONFCLOUD-59001 ! We're all so eager to see you grow, but we really just want you to be completed 

Also experiencing this! Really need to do the PDF print of these and can't change to full width because I use the support portal. Any word? This is a major pain point.

My entire page cuts the left side off.

Any update on this bug? This is a major bug which makes our knowledgeable unusable for sharing outside of a direct link (read: Senior Leadership).

Any update?

+1 on requesting to change priority, this isn't a minor bug. The export is unusable.

Experienced it today, we had to manually edit dozens of pages to make them full width after we realised that's what caused it, before we could all export them... and then re-edit them so that they look normal in the web view. That's an easy workaround when you have to export one page, but not when your entire site uses single column template cause it's mostly text.

+1 vote to hire Trent!

Just going on your own guidelines about what constitutes minor: "

• visual defects, that don't affect function

I'd say chopping off text from exported pages does affect function; the function of reading the documents.

Then you've got a point in Major

• application is functional, but frequently used gadgets or macros don't work

Is PDF generation not frequently used?

The response from the team on the forum was "Only 5 people have voted, it's not a big issue". Not everyone who encounters a problem actually does anything about it - they just sit there and seethe, then abandon their efforts and submit; but it leaves a pretty crappy taste in one's mouth.

Open source the component and I'll fix it myself  

Is there a way to increase the priority of the issue? It's already opened for 8 months.

This problem is important to solve, in my organization it causes us a lot of repetition because the generated in confluence is sent to the clients and we have to export to "Word" and accommodate it again.

I also ask, when do you think you solve this?, The confluence is very dynamic, but without solving this problem it becomes limited.

Any idea when this bug may be fixed? It just seems unusual to the point of absurdity that something like this can firstly go out the door in a widely used, production system, and secondly that actually padding the sides of the content on the page results in the PDF chopping the side of it off - if anything, I would have thought it would centre the content on the PDF.