Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-78986

Incorrect Rendering of Macros Within Tables in Legacy PDF Export Functionality

      Issue Summary

      By including the "@page" tags in the PDF stylesheet, the PDF export functionality reverts to the old experience instead of utilising the new PDF export experience, as discussed here. This legacy exporter does not effectively render few macros within tables, resulting in formatting issues in exported documents.
      This issue has been reported for the following so far:

      • Bulleted lists
      • Action items
      • Jira Issue Macro

      Watch our progress on export features to see future updates.

      Steps to Reproduce

      1. Customise the PDF stylesheet by adding the @page tag with @top-right, @top-left etc.
      2. Create a Confluence page containing a table and bulleted list and/or Task and also with Jira Issue macro.
      3. Export the page to PDF using either page PDF export or space PDF export.
      4. Observe that the bulleted list/Task within the table column will be incorrectly displayed in the PDF Export.

      Bulleted list within table test.pdf

      Expected Results

      The bulleted list and/or task within the table is exported correctly.

      Actual Results

      The bulleted list and/or task within the table is exported incorrectly.

      Jira Issue macro shows as URL link instead of a table

      Workaround

      At present, there is no identified workaround for this issue. The only resolution to address this issue is to remove the custom CSS, allowing the PDF export to utilise the new PDF experience.

            [CONFCLOUD-78986] Incorrect Rendering of Macros Within Tables in Legacy PDF Export Functionality

            Hi everyone,

            This is Joe from the Confluence team. This bug is fixed for all exports except for space exports with more than 2000 pages (0.03% of exports). We have confirmed the functionality to be working as expected for all other exports.

            Sincerely,

            Joe Larson

            Joseph Larson added a comment - Hi everyone, This is Joe from the Confluence team. This bug is fixed for all exports except for space exports with more than 2000 pages (0.03% of exports). We have confirmed the functionality to be working as expected for all other exports. Sincerely, Joe Larson

            Hi 8ce589c54c0a.  Thanks for your update.  Do you have any further updates since we are now into November?

            Rusty Lundgren added a comment - Hi 8ce589c54c0a .  Thanks for your update.  Do you have any further updates since we are now into November?

            Hello everyone,

            This is Joe Larson from the Confluence team. Thank you for your patience as we work on fixing this bug. The bug has taken longer than expected for us, and we are currently forecasting resolution by end of October 2024, or sooner if possible. We know you have been waiting eagerly for this fix as we are, and we will be providing any updates as they come. Thank you again for your patience!

            Best,

            Joe Larson

            Joseph Larson added a comment - Hello everyone, This is Joe Larson from the Confluence team. Thank you for your patience as we work on fixing this bug. The bug has taken longer than expected for us, and we are currently forecasting resolution by end of October 2024, or sooner if possible. We know you have been waiting eagerly for this fix as we are, and we will be providing any updates as they come. Thank you again for your patience! Best, Joe Larson

            I would love an ETA for this fix as well.

            Rusty Lundgren added a comment - I would love an ETA for this fix as well.

            Can anyone provide any update or an ETA on when this might be resolved? Almost a month since I posted, and absolutely no traction in getting this fixed.

            Lee Suddeath added a comment - Can anyone provide any update or an ETA on when this might be resolved? Almost a month since I posted, and absolutely no traction in getting this fixed.

            I don't see any way to perform the remediation that is described above. Going to the cog icon doesn't present an option for Look and Feel. If I go to System, there is a look and feel, but no PDF export settings? In the meantime, I have users unable to export accurately. What is the expected ETA, now that this has been opened for over two weeks?

            Lee Suddeath added a comment - I don't see any way to perform the remediation that is described above. Going to the cog icon doesn't present an option for Look and Feel. If I go to System, there is a look and feel, but no PDF export settings? In the meantime, I have users unable to export accurately. What is the expected ETA, now that this has been opened for over two weeks?

            Yusi Liu added a comment -

            also, when exported PDFs can have bookmarks? such basic and simple feature , been missing for years and years ... 

            Yusi Liu added a comment - also, when exported PDFs can have bookmarks? such basic and simple feature , been missing for years and years ... 

            Yusi Liu added a comment -

            After three days of intense escalation, there's no solution - we were asked to remove the PDF stylesheet, and that's it. There's no timeline for a fix yet... 

            Yusi Liu added a comment - After three days of intense escalation, there's no solution - we were asked to remove the PDF stylesheet, and that's it. There's no timeline for a fix yet... 

            We are using the CSS stylesheet for exporting PDFs and our bullet point lists and then numbered lists were off (we don't use checkboxes, but the following should work for those entries as well I assume).

            For me, adding a padding for unordered lists helped as a workaround:

            .wiki-content table ul 

            {          padding-left: 50px;    }

             

            I just then also had to set a tiny padding for the ordered lists, to limit their shifting to the other side (in our CSS, we use the list-style-types decimal, lower roman and lower alpha):

             

            .wiki-content ol, .wiki-content ol ol ol ol, .wiki-content ol ol ol ol ol ol ol, .wiki-content ol ol ol ol ol ol ol ol ol ol 

             

            {          padding-left: 1px;        }

             

            The padding value can be adjusted as needed.   

            Anna-Lisa de Oliveira Löhrer added a comment - - edited We are using the CSS stylesheet for exporting PDFs and our bullet point lists and then numbered lists were off (we don't use checkboxes, but the following should work for those entries as well I assume). For me, adding a padding for unordered lists helped as a workaround: .wiki-content table ul  {          padding-left: 50px;    }   I just then also had to set a tiny padding for the ordered lists, to limit their shifting to the other side (in our CSS, we use the list-style-types decimal, lower roman and lower alpha):   .wiki-content ol, .wiki-content ol ol ol ol, .wiki-content ol ol ol ol ol ol ol, .wiki-content ol ol ol ol ol ol ol ol ol ol    {          padding-left: 1px;        }   The padding value can be adjusted as needed.   

            AKwilasz added a comment -

            We definitely need a fix for this ASAP - it directly impacts our workflow!

            AKwilasz added a comment - We definitely need a fix for this ASAP - it directly impacts our workflow!

              Unassigned Unassigned
              c2d78d0f7204 Amin A.
              Affected customers:
              29 This affects my team
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: