NOTE: On November 14, 2022, we rolled back the Confluence PDF export feature to its previous implementation. We understand the rollback may impact the performance of this specific feature. We appreciate your patience and understanding while we address the issue.
We will post an additional changelog entry when we are ready to resume the rollout of the new export.
Hey everyone, Nitish here from the Confluence Cloud Migrations team with an update on significant improvements our team has been making to PDF exports! Check it out on the changelog and let me know if you have any questions or concerns in this thread or via a direct message.
Hi @NitishMidha,
Is there any way to have access to the changes before the releases? So that we can anticipate if we have any compatibility to do before Confluence releases. Many thanks for your help!
Hi,
does this involve any changes to the export_view content format or CSS batches as produced by the /contentbody/convert/export_viewREST API?
We’re heavily relying on this API in most of our Confluence Cloud apps and any unannounced changes to the data format might break features in our apps.
@NitishMidha Hey, according to the post the feature should be rolled out for 100% of the instances by now. For us, it only works on one of our Confluence instances, while it doesn’t for all others. Can you verify that it’s rolled out for everyone?
Hi @NitishMidha,
PDF is still not working for us. It works perfectly fine for some of our instances, but for others, we now get just the text “extension” instead of our macros. Is this a known bug?
EDIT: This bug happens only on “Overview” pages. It works fine for all other pages.
Hi @NitishMidha,
This improvement is really cool. The only thing we found is that dynamic content macros can be exported before they are ready. So in my case I see a spinning wheel instead of a chart in case of a heavy content. Is there any way to flag the macro is ready?
P.S. Did I get it right the headless vrowser is used to render the page for export?
Also, exporting as pdf no longer applies the custom CSS we put in “PDF stylesheet” (whether it’s in the global settings or the spaces setting). Has this been disabled on purpose?
Hi @eazyBISupport, thanks for making the change, we noticed that eazyBI chart doesn’t automatically resize when confluence window gets resized, hence causing this issue of table not getting printed fully onto the PDF. I’ll check with team if the change has fixed it completely or if their’s anything else required.
Hi @NitishMidha
Yes the error is still happening and it happens in all spaces for the overview page. You can try it out yourself in our public documentation:
Overview page (doesn’t work, just says “extension”): Confluence
Other Space’s overview page (also doesn’t work): Confluence
Hi @NitishMidha,
I tried to reproduce the issue today and found it is working much better than a week ago. I created a very heavy page and reproduced the issue twice, but the other 10 times it worked correctly. That’s really good. See attached pdf (one is OK, and the other one is with the issue). _akhaneev-Export issue Demo-201022-110959.pdf (224.5 KB) _akhaneev-Export issue Demo-201022-110906.pdf (33.5 KB)
I still want to understand how it detects the macro readiness when exporting the page to pdf. Just want to be sure how it handles cases when there are asynchronous requests to Confluence REST API (especially the new async REST API).
Thanks,
Andrey