Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-26210

Export PDF does not render {attachment}, (attachment macro)

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Problem

      When exporting a page to PDF, the attachments macro renders garbled information, making it impossible to read.

      Workaround

      There is no workaround yet for this problem

        1. 1.png
          1.png
          26 kB
        2. AAAAA-010812-1120-57.pdf
          15 kB

            [CONFSERVER-26210] Export PDF does not render {attachment}, (attachment macro)

            Minh Tran added a comment -
            Atlassian update

            Thank you for taking the time to raise, comment or vote on this Bug. Currently this bug indicates that it only impacts a version of Confluence which is no longer in support, therefore we are closing this issue as Timed Out.
            If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue.
            Thanks again.
            Regards,
            Confluence Development

            Minh Tran added a comment - Atlassian update Thank you for taking the time to raise, comment or vote on this Bug. Currently this bug indicates that it only impacts a version of Confluence which is no longer in support, therefore we are closing this issue as Timed Out. If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue. Thanks again. Regards, Confluence Development

            I agree with Bruce. While it is good that it is partially resolved in 5.1.3 we are on 4.3.7. This is making a large number of our page exports to PDF unusable in any form. This should be fixed in at least 4.3.x and 5.0.x.

            James Roberts added a comment - I agree with Bruce. While it is good that it is partially resolved in 5.1.3 we are on 4.3.7. This is making a large number of our page exports to PDF unusable in any form. This should be fixed in at least 4.3.x and 5.0.x.

            It is good to hear that this is partially resolved in 5.1.3. But we are still on 4.3.2 and would like to know if there will also be a resolution for this version.

            Bruce Schlueter added a comment - It is good to hear that this is partially resolved in 5.1.3. But we are still on 4.3.2 and would like to know if there will also be a resolution for this version.

            Hi all

            This issue is partially resolved in Confluence 5.1.3. The remaining problems are being tracked under https://jira.atlassian.com/browse/CONF-29801. As CONF-29801 provides a better description of the current problems with the attachments macro in PDF's I'm closing this issue out as obsolete.

            Regards

            Steve Haffenden (Inactive) added a comment - Hi all This issue is partially resolved in Confluence 5.1.3. The remaining problems are being tracked under https://jira.atlassian.com/browse/CONF-29801 . As CONF-29801 provides a better description of the current problems with the attachments macro in PDF's I'm closing this issue out as obsolete. Regards

            We are affected as well. This a bug and should be fixed. Also priority 'minor' does not seem to be appropriate IMHO.

            David Toussaint [Communardo] added a comment - We are affected as well. This a bug and should be fixed. Also priority 'minor' does not seem to be appropriate IMHO.

            Why is this a 'minor' bug? This error is making the export to PDF unusable!

            Harald Mueller added a comment - Why is this a 'minor' bug? This error is making the export to PDF unusable!

            Same here. It should just work.

            Marcel Plomp added a comment - Same here. It should just work.

            We also run into this problem. Will there be a workaround or solution?

            Bruce Schlueter added a comment - We also run into this problem. Will there be a workaround or solution?

              shaffenden Steve Haffenden (Inactive)
              gcheck GuilhermeA
              Affected customers:
              7 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: