-
Suggestion
-
Resolution: Unresolved
-
59
-
-
The new PDF export experience does not currently support @page tags with @top-right, @top-left etc properties in the PDF stylesheet and header/footer/title html that can be used to modify space PDF exports:
- https://support.atlassian.com/confluence-cloud/docs/advanced-pdf-export-customizations/
- https://support.atlassian.com/confluence-cloud/docs/customize-exports-to-pdf/
If any of these are present, it falls back to the old PDF export experience which does not export PDF pages as accurately.
Also if ip allowlisting is enabled, pdf export will fall back to the old PDF experience. (IP Allowlisting is supported now for the new PDF export experience)
This ticket is to track the support of @page tags with @top-right, @top-left etc properties in the PDF stylesheet and header/footer/title html for space PDF exports and support for ip allowlisting through the new PDF space export experience.
Related:
- is cloned from
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
[CONFCLOUD-76035] Support @page tags with @top-right, @top-left etc properties, header/footer/title html in space PDF exports for new PDF export experience
We have been diligently addressing these issues throughout the week. You can anticipate the final improvements to be implemented by the end of the day. Furthermore, we will be updating the in-product messaging and documentation in the forthcoming weeks.
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
{ content: "RESOURCE"; font-family: ConfluenceInstalledFont, Helvetica, Arial, sans-serif; color: #c91616; font-size: 13pt; font-weight: 400; display: block; margin-bottom: 10px; }/* 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
Hello 8bc977c59aad,
Are there any updates on the status of the feature? What has already been resolved? There is any planned due date?
Thanks.