Hello 8bc977c59aad,

Are there any updates on the status of the feature? What has already been resolved? There is any planned due date?

Thanks.

+1

Hello,

Can we have some update on this issue?

A due date for a fix, workaround or rollback can be good.

3efb106ab75f there is a separate Bug logged for the table issue CONFCLOUD-80335 Tables in PDF Export Display Shadows and Extra Lines - Create and track feature requests for Atlassian products., hopefully this gets resolved by the expected date of 10th Jan 2025 as it's a major headache for us too.

Our organization is also suffering from this PDF export issue. I have tried updating the style sheets to fix the table display shading error but nothing would fix it. With this complaint not being taken seriously we are likely to move away from Confluence now.

Please rollback this change. Our PDF exports now look terrible, and we've put much work into customizing them for exporting to clients.

Since 2021 we have had css in place for the PDF export to add 2 pseudo classes to the H1 to generate a "cover page" on single a page exports. Those are no longer working and there's no clear work around from an hour of reading documentation. Instead of adding the pseudo class content as a BLOCK it is adding them inline, which is not the desired visual outcome.

CSS Used:

/* TITLE PAGE - using page H1 */
h1

h1::before

/* TITLE PAGE - decoration bottom */
h1::after

As the vendor of eSign for Confluence I can confirm that the latest Atlassian PDF exporter update did break inclusion of app dynamic macros.  They work in Export to Word,  but not Export to PDF.   Even with default (blank) Space Settings > PDF Export CSS.

Recommend rollback on this recent engine change until the problem is fixed.

Sincerely

Chris Cairns
Digital Rose

We also use the @page function to display images. Please fix.

We use the @page function to display images. Please fix asap.

New upgrade broke our key ability to include esignature which is a production blocker.  so please fix this asap.

Atlassian:

• Please reclassify Type as a bug, not a suggestion. A ticket for broken functionality is a bug.
• Please link Description to Anna-Lisa's related ticket: https://jira.atlassian.com/browse/CONFCLOUD-80176
• We await your progress on this important functionality that reassures our users that their exports containing sensitive information came from our site.

fc73b0d3205f 

It seems that a config update broke this part of the export functionality, we tried different things and couldn't find a workaround/fix. I filed a support request and therefore the following ticket was created (please support this with your vote):

https://jira.atlassian.com/browse/CONFCLOUD-80176

Somewhere I also saw this ticket's due date (hope they fix it this soon):

Thank you! Anna-Lisa

Hello,

up to now, we have displayed a background image in the header of our exported PDFs that covers the entire width. This also worked on Confluence Server in the single export. In addition, a logo is displayed for space exports.
Can anyone tell me what I need to do to make this work in Confluence Cloud (besides paid apps)? No matter whether Legacy or New Editor, with or without @page, single or space export.

Thanks! Volker

We have the same issue. Last month it was working. Our reports generated for customers are without logos and @ page tags this months. This functionality was working for several years in our configuration. Atlassian please fix it. Thanks. 

Pictures don't occur when I export my file to PDF. Can anyone fix this issue?

This is so confusing.   I'm not bothered about the format of the "full space export".....I had our space configured so that if you exported a single page the company logo was included in the header.  I followed the instructions available on this site, and it worked well for years.

Now when you export you get the cryptic message indicating that if you reference the @page element it will use the "old" PDF engine.    Well, that's fine....the old engine worked well enough.   But I don't get the logo on the top of the page, so it looks like the "old" engine is broken now?  I haven't changed the CSS i originally configured back in 2021.

So..... for my understanding..... they brought in a "new" engine, that still doesn't have the capacity to include a logo image in the header AND cannot use the old @page method to "trick" the engine into including the image....is that right?    And then at the same time somehow broke the old engine so that no longer works either?

There are pages on the Community knowledge that are still telling you to use the @page approach....<brain explodes>   I've got SO many more better things to be doing with my time!!!

Atlassian, provide us some clarity please?

The same thing happens to us. We use custom CSS that is now completely ignored, and using the default export does not create decent PDFs. 

I hope this will be solved soon

I also need help correcting this PDF export look and feel issue. We are relying heavily on Confluence documentation, which we need to update to another application and the current style is not compatible with the endpoint. This is a blocker. 

I was using a custom CSS which worked well up until last Tuesday. I did not make changes to my PDF CSS. 

This needs to be implemented ASAP. The current functionality sucks...

+1. It's absurd that this is not already fixed. The "new" editor is already several years old. How can it be missing basic functionality like this?

please accelerate the development of this

This feature is necessary for some of my use cases, please implement it. Also, the fallback does not work when exporting a single page for some reason. Please fix this.

Given that a Single Page export ignores Headers/Footers and even referencing them in the stylesheet does nothing for me, while also having no support for dynamic content in the Header/Footer wiki-markup settings the pdf export is almost useless for anything then data transfer.

Without paying extra for addins you can not get a single page export to look good enough for any external use.

Having a Header with a dynamic title and/or a logo or something similar is standard export behavior needed everywhere and I can not understand how this is not a basic that is implemented asap. A documentation tool without an export that you can show externally is not a real documentation tool.

On another note: Here is what I tried:

Header: <img src="/download/attachments/SPACE_ID/Logo.png" alt="Logo" style="height:50px; vertical-align:middle;" />

Stylesheet: img

This will not show in any single page export, only space export. A second point I still do not understand: How can this differ and why is it so hard to implement it, if it is working with space export?

Any news on this? We are generating lots of sensitive documentation using the exporter and for a while now they look really terrible. We really need to upgrade to the new experience, but impossible without supporting the tags first.

Thanks for the tip a57b0748fc61 . But the color issue is a big issue.. We use colors to differentiate visually between user profiles, and half of the panels appear without colors in the PDF export.  Also the labels inside the tables also appear larger that it is. while using the new PDF export, appear smaller.

The color issue along with the size of some texts has made me think that maybe I should go for V2 and look for an alternative solution for the title, header and footer.

3e7e8bd58fa2 
For me, adding a padding for unordered lists helped as a workaround:

.wiki-content table ul

I just then also had to set a tiny padding for the ordered lists, to limit their shifting to the other side (in our CSS, we use the list-style-types decimal, lower roman and lower alpha):

.wiki-content ol, .wiki-content ol ol ol ol, .wiki-content ol ol ol ol ol ol ol, .wiki-content ol ol ol ol ol ol ol ol ol ol

The padding value can be adjusted as needed.

The only thing that still does not work is the different disc style for sub levels of the list.
And I did not find a solution for the color issues.

6052b77cb806 which css? If I use this one https://confluence.atlassian.com/confcloud/files/724764825/724764826/1/1427771626612/confluencedefaultpdf.css it fallback to V1 PDF render, since it use @page, and I have issues with the alignment of text with bullets inside tables  and some colors of info panels

Hey guys,

i can provide you at least something here to have a Logo, top- and bottom-divider as well as page number an footer content. Check out the PDF.

https://nc.planzeit-service.de/s/zoSdqp5XKd5nBH9

Insert the whole css into https://<your-atlassian-url>/wiki/admin/pdf-export PDF stylesheet.

Upload a logo to one of your sites and change the id. If necessary, upload a custom font as well.

The title, header and footer are needed in order to provide this information in all the PDF exported. It should be mandatory to release a new version (v2) with, at least, the same functionalities of the previous one. Exporting with previous version has some issues with color panels and text with bullets inside tables... Please, fix it ASAP.

bb48e04296fc This particular issue is still in the "Gathering Information" stage.  No one is working on it.  They are waiting for more votes, or possibly for the people who want this to retire or die of old age.   There are numerous examples of simple fixes and features that have been in development for over 7 years.   This one has "only" been around for a little over a year.  So vote for it, and don't hold your breath.

I am in urgent need of adding header and footer info as part of export pdf. I am failing in doing so. Even when we add an image on a template and try pulling the template into the page. The added image doesn't show up, but intern show an error "Preview Unavailable". Atlassian team Please provide us with some solution. Just this month we are planning to upgrade Jira and confluence subscription. Expecting this to get resolved asap.

Is there a timeline/roadmap for getting this implemented?

Mirroring recent feedback, our team requires the inclusion of header and footer details in single-page PDF exports.

Displaying attribution in footers is essential for our documentation compliance.

Manually editing each page in our spaces to include the attribution within the page's content would be highly impractical and labor-intensive.

Is there a way to display footnotes on every page in PDF exporting?

Is there a page somewhere that summarises the current status of PDF export?  Reading the comments here people have tried various things with limited/no success, this is often following official help/guidance materials from Atlassian.  But it seems that guidance is incorrect or out of date.  Can we have that corrected before I waste time trying to set something up that is known to not work. The fact some of these tickets go back so far is a real concern.

The lack of branding when we export content is a significant issue for us.  It blocks us using confluence for some types of content, the impact of this is we end up with no single point of truth and it undermines confluence use more generally.

I have try everything from here

https://support.atlassian.com/confluence-cloud/docs/customize-exports-to-pdf/

https://confluence.atlassian.com/doc/export-content-to-word-pdf-html-and-xml-139475.html

https://support.atlassian.com/confluence-cloud/docs/export-content-to-word-pdf-html-and-xml/

https://confluence.atlassian.com/doc/customize-exports-to-pdf-190480945.html

However, it doesnt help at all.. the content size show very small, not same as before.

the font size too small, table not show fully width even in the page had make it in full width. 

how im going to share the document to client when the content too small to read?

I agree to @John Tolle, there are now two broken PDF exporters...

Please atlassian, fix this immediatly!

We are laughed by other users, partners and customers, which run confluence onpremise... They can indeed create beautiful PDF - we are not even able to insert our logo into the header.

It is not funny anymore.

This error gets us into very big trouble. We have so many pages that are affected here and are currently unable to provide our customers with correct PDF documents.
It is therefore urgent that the problem is solved as quickly as possible.

Come on, guys! A professional user of Confluence needs a way to produce a professional output of pages!

How is one expected to deliver content to a customer that way?!?

+1, my users have reported work disruptions due to this change.

In addition, the stylesheet CSS template override does not seem to convert to using the old style on my instance - would be happy to receive any feedback on how I can make that work as expected (just want A4 sizing back). This is the value I have entered in the CSS template field:

@page
{
size: 210mm 297mm;
} 

Output is still letterhead 8.5"x11".  I am using the space-level override, not the global one - international company, can't make it by fiat.

It's great that I can finally do something to improve how pages are exported to make for better print friendly documents. Until I realized I did all this and the captions on my images do not show up. And I can't seem to find any work around other than going back to all these images (hundreds of pages) and adding text instead of using Confluences built in caption. Feels like a waste to not have this element editable by users. Either I use the default export style with captions but can't seem to customize anything worthwhile. Or I add some customization that results in the older export style with no captions. Waiting hopefully for an update to correct this issue.

The problem I see here is that there are now TWO broken PDF exporters.  You either get one that exports the contents properly (the new version) without proper control over the header and footer or you get one that fails to export many parts of the content properly (the old version) but with full control over the header and footer, for things like company logos.  Or am I missing how you can do things like put company logos in headers in the new version?  Sure, there's a header section where you can add text, but I do not believe you can put images anywhere but in the CSS, which doesn't help with things like header or footer images since that's the subject of this issue.

To clarify, the old Customize exports to PDF page does mention IMG tags in something like the Title page, but the contents of the Title page field doesn't seem to appear in the new PDF renderer at all, even if it's just some plain text.  In fact, none of the content in Title, Header, and Footer fields appears with the new PDF renderer.

Perhaps they used to before the related CONFCLOUD-77777 was just resolved?

@Gerri Mills  apparently the page size defaults to a size where your server/instance is located 

Page Size

The default page size is based on the location of your Confluence instance. For example, if this instance is located in the US then the default paper size of your PDF export will be US Letter (8.5 inches wide by 11 inches long). If the instance is located in Australia, the default paper size will be A4 (210 mm wide by 297 mm long).

There is more information here about customizing the stylesheet. https://support.atlassian.com/confluence-cloud/docs/customize-exports-to-pdf/

How do I change the page size of a pdf export now?

I don't think I can do this anymore:

@page { size: 210mm 297mm; }

In Australia we use A4 by default, but my exports are Letter page size

I would also include any customisations that have been set in the "Page layout" tab (Header & Footer) when exporting to PDF. That would save time and give more flexibility.
For regulatory compliance, it is advisable to be able to add the date and time as a timestamp.

We don't see the table of contents anymore on exported pages. Is that due to this issue here or did we do sth. wrong?

Please get some of these basic layout features working for PDF export. We have confluence content that needs a bit of styling, and we desperately don't want to have to invoke our design process just to apply headers, footers, logos, etc., etc... 

It also seems that the former stylesheet does not support image anymore... do you have the same experience ?

The PDF Export should also contain possibility to add page numbers, visible page information and printing date/time in addition to headers, footers and page title etc. These are quite basic requirements for good document control softwares.

I wonder why the "gathering interest" stage is needed to preserve a long-standing feature. The new PDF export version should not have been released without supporting the existing customization features.