New PDF export experience breaks dynamic content macros

Confluence Development Confluence Cloud
1

Hi all, heads up that one of the recent changes in the new PDF export experience has broken dynamic content macros across two of our Confluence apps in 4 of our 8 test environments and has been reported on several customer sites.

It appears that sites with the new engine skip embedding content macros (servers never receive the export request). The MS Word export works fine.

This is breaking for our signature app customers as they use this to display signatures within exported pages.

Atlassian ECO support has raised a bug: https://jira.atlassian.com/browse/CONFCLOUD-80251 but so far have not published an incident. ECOHELP-52585

If you have dynamic content macros in your apps recommend testing your PDF exports.

Chris Cairns
Digital Rose

PS. And numerous customers have raised concerns and problems with this “new” PDF export: See https://jira.atlassian.com/browse/CONFCLOUD-76035. It looks like this change was released before being fully baked.

3 Likes
2

I don’t know how it works now, but really the PDF export feature should just load the page in a headless browser and take a screenshot.

Or if text search is necessary then do that individually for each iframe on the page and replace in PDF with a screenshot.

3

Thanks @nathanwaters . We use the Macro render mode to support exports (https://developer.atlassian.com/cloud/confluence/modules/macro-render-modes/). Instead of the headless browser Confluence will call our servers and ask for an XHTML rendering of the macro in storage format.

At least that is how it used to work. :slight_smile:

1 Like
4

Update: The Atlassian dev team found and rolled back the change the caused this problem. PDF Exports are working again.

Thank you Atlassian

2 Likes
5

Thanks for keeping us informed @Chris_at_DigitalRose. :sweat_smile: