On some Confluence instances, our macros are not visible in the rendered PDFs, however, on others, they work perfectly fine.
I wanted to debug this locally, but when using ngrok to install the app on a development instance and running a PDF export, Confluence does not even send any request to our app to render the macros but just puts “extension” as text in the document.
I have no idea what is going on here. On top of that the PDF export stopped working on one of our own instances without updating any code within the last few days. Is there an issue with Confluence? Does anyone else have this problem? Any suggestions on how I could debug this better?
The issue has been resolved. Please let us know if you still see any problems and, if you can, we would also appreciate if you could confirm if the problem is resolved for you as well.
@ccurti
Thanks but this actually made things worse for me.
Before the change:
PDF export would work perfect for some instances and not output anything for other Confluence instances
We didn’t use render-modes for most of our macros, and it still worked!!! As mentioned, only on a couple of instances, but at least it worked sometimes.
After the change:
PDF exports don’t work anywhere, even on the Confluence instances where they used to work
Even when using render-modes, Confluence does not output anything
To clarify, on our end the change I mentioned in this post has been completely rolled back so the behaviour described is something else.
I would recommend asking the affected customer (or you directly if this is affecting one of your sites), to reach out to the Atlassian customer support team (Atlassian Support) with the following details:
the link to one page that is failing
site URL
While I’m mostly familiar with the render modes implementation and not the standard one, I had a look for known issues around exporting to PDF and this is what I could find: