I have a simple confluence page. No tables, just a table of contents at the top and some header hierarchy. Single column layout. When I export to PDF, all but the top header have the leftmost character or two cut off in the margin of the page. Any ideas why or how to fix it?
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)
size: 216mm 279mm;
width: 190mm !important;
align-self: center !important;
margin: 18px !important;
Hi there Atlassian, we have this issue on every PDF export we do in our team of 20. We're using confluence cloud and ive seen this issue for the last 3 months.
Is there really nothing you can do? It seems like a pretty simple and important thing to fix.
Cheers, have a lovely day
I can confirm that this issue is still happening for us as well.
Even with the top CSS fix applied, it aligns the left side of the page but still cuts off on the right.
I agree with Greg and Jordan's frustration. A feature that doesn't work as indented isn't available.
Is there any news on this being fixed? Thanks for any information you can provide us with.
For reference, we are using Cloud.
Just in case you haven't found a solution yet. I had the same problem with the right side being cut off with the above fix. I just edited the CSS since the page widths minus the margins were wrong. Code is below that worked for me, hope it helps.
size: 216mm 279mm;
width: 168mm !important;
align-self: center !important;
margin: 18px !important;
This is still broken a year later.
If the person you want to work with doesnt have a confluence licence or is a low level user there is literally nothing you can do to collaborate with them. I have invested so much time into Confluence I want to cry. I agree with Jordan Smith from over a year ago, this destroys the value of confluence.
If you watch the bug ticket linked (CONFCLOUD-59605), then you will receive any updates there once there is progress or any further workarounds.
If you want, you could also comment there with your question above about adding CSS rules; perhaps someone is able to help come up with a workaround using that theory.
Here are two examples. One when I export PDF using "Single Column" layout, which cuts off left edge, and one where the only change is to switch to "Full Width" layout, which works fine on paper, but is not very usable when viewed online on a wide screen, because it makes extremely long lines that are hard to read.
I tried to replicate this on my Confluence instance, single column layout, but I'm not able to.
Can you confirm your Confluence version? Maybe that makes a difference. Also, can you let me know if it happens on all pages or only certain ones? Do you have all custom PDF export CSS turned off?
Thank you for confirming.
So I'm not able to replicate this on my own instance, and as a support engineer, I'm also able to see the one that is associated with your email address. If that is the instance that you're having an issue with (vi****.atlassian.net), I am also not able to replicate the issue there.
Can you just confirm, you're going to the page, click . . . and then select Export to PDF, correct? Using this method, I am not able to get any of the PDF cut off in the end result.
Are you able to provide me with the title of a page on your instance where you're currently able to replicate the issue? You can make a test page if you like so I can test with that.
Lastly, can you confirm this is happening in all browsers? I'm trying right now with the latest Google Chrome release.
This is why I suggested that you make a test page on your instance with a generic title, add some data to that page, and confirm that you have the issue there.
Then you can provide me with the name of the test page so I can have a look.
Can you also clarify what you mean by full width vs single column? When you enable single column in page layout, saving the page will remove that since a page is already in single column layout.
Okay, there are two demo pages here: https://vivint.atlassian.net/wiki/spaces/~358430864/pages
Here are screen shots of the PDFs I get out from Export PDF, using the method you describe above.
Below them is a screenshot of what I mean by Full Width vs Single column. To recreate, Edit a page. In the top bar, there's a Page Layout icon (box with two rectangles inside it). Click that, and it brings up the Layout bar, as shown in the screen shot. The first icon in the bar is the Full Width (default) layout, and I'm hovering over the Single Column layout.
The _only_ difference between these two pages, after I copied the Full Width one, is the title, changed for clarity, and the Layout switch.
Please confirm you can duplicate this.
Browser: I'm using Chrome Version 65.0.3325.181 (Official Build) (64-bit) on OSX at the moment, but since the PDF export happens on the server side, it doesn't seem to be dependent on my browser or OS.
Thank you, Mac!
Apologies for that, as it appears the layout options had not been available in my Cloud instance (and of course not Server as it's not an offering for that). The previous Single Column Layout was what is now the Full-Width Layout. I do now see the options on your instance and I was able to test properly.
I searched this, and I found a bug ticket that sounded very similar to the issue you were encountering. I've cleaned it up a bit to describe the exact behavior and you can find the bug below:
I discovered that I am not able to replicate the issue with other page layouts as well. In addition, if I enter the text into a single Fixed Width table cell, I can somewhat replicate the appearance of a Single Column Layout. You can try this as well, but unfortunately, it will not work if you need to include another table inside of the layout.
Lastly, I noticed our documentation on Add formatting to your page does not mention the new version of Single Column Layout so I have requested a documentation update here. It's probably not relevant to you since you were already able to find it, but I'm including it in case other users do not know it's an option now:
Thank you for all your patience and help in tracking down the cause of this issue. I would recommend that you watch the bug so you can be updated of any changes. Do let us know if you have any questions!
Hello there, @Balirka!
The bug is currently low because it hasn't been prioritized any differently. You can see the bug currently has 5 votes and 5 watchers, and so it can appear that not very many customers are running into this issue.
We prioritize bugs according to the following:
I encourage anyone who has run into this issue to please vote on the bug to help show the number of users encountering it, watch it, and comment there with your findings. That will help us to properly prioritize the bug.
Thank you for your understanding!
This should be high priority. It's honestly such a problem that we're considering moving our knowledge base to another platform. It's frankly unacceptable you'd let such a simple bug continue on like this. As it stands, your PDF export is BROKEN. You essentially have no PDF export.
@Shannon According to the bug fixing policy you linked, this should be a Severity 2 because the feature is unavailable. And, by unavailable, I mean it does not produce a fully legible PDF document with all the words in it. It would be available if it actually worked, perhaps with cosmetic errors. But, missing data is not a cosmetic error. This is completely not usable. It is not available to us as a feature we can use. So, it is a Severity 2 bug... still after almost two years.
Thank you for bringing this to my attention.
Now, I can't say for sure since the development teams handle the prioritization of bugs and feature requests, but from what I can tell, it would likely be classified as a Severity 3. The reason is that the the PDF export feature itself is still available, and this issue is only encountered when using a specific page layout. If users weren't able to export to PDF at all, under any circumstance, it would be classified as Severity 2.
There also appears to be a workaround provided by @Steve Ostopchuck at the start of this thread. Were you able to test that?
The hack works, but, we don't know yet what if anything it breaks. So, now we just need to apply that hack to every Space in our world and train all our users to set that up on each new Space they create. Well, we could wait until something doesn't work for them and they submit a help ticket and...
We also see that if the page does not have problems if we don't use any layout elements at all. But, if we use any, then the only space for single column content is between layout elements and this is the stuff that has the left edge clipped. And, since you have taken away the ability to add a layout element and set it to single column, there is no trick for laying out pages that avoids the problem.
The workaround is survivable for a short period. It has been a long time now. And the new page editor seems to drive us more often to hit this problem if you count on exporting documents to PDF, which we do. Come to find out, the workaround my folks have been using is to copy the entire page into a Word document, fixing it up there and exporting that to PDF. Yikes.
I'm testing this in my Global PDF Stylesheet, and when I apply it there, if I export the page again, it's not cut off. Can you try that and see if it prevents you from having to apply the workaround to each space?
I also wanted to mention that I tested this in the 2 and 3 column layouts on the new editor, and I was not able to replicate the issue there, only when using the old editor with the single column layout. Can you let me know under which circumstances the issue occurred for you?
As for the workaround, it appears to just be re-adjusting the margins, alignment, and font size. This shouldn't cause too many issues, but it's definitely a concern.
I am unable to attach images here. When I click the Reply button the browser indicates it is waiting for Google Analytics and we never get past that.
Reproducing the failure is very simple.
Notice the stuff you entered outside the 2-col element is clipped on the left.
I guess the design intends to assume anything outside a layout element is single-column area. Which makes sense. But, since it doesn't work and there is no 1-column element for us to insert, the only workaround is to hack the CSS for every space
This past summer, we joined forces with Microsoft Teams as a part of our mission to help your team collaborate better, starting with more effective meetings. We released a new and improved Confluence...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events