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

PDF export: Links in Children Display Macro do not generate intra-PDF links, redirect to live Confluence pages instead

XMLWordPrintable

      Issue Summary

      When exporting a Confluence page (created in either the new Cloud editor or legacy editor) that includes the Child Items(Child pages) Macro, the child page links listed in the macro do not behave as intra-PDF links. Instead of jumping to the corresponding page within the generated PDF file, clicking the child page links redirects the user to the live Confluence Cloud page in the browser.

      This behavior has been confirmed across both editor types and does not align with the expected intra-PDF linking behavior established by recent PDF export improvements (e.g., CONFCLOUD-56581 and CONFCLOUD-80393).

      Steps to Reproduce

      1. Create a parent page in Confluence Cloud and add several child pages beneath it.
      2. On the parent page, insert the Child Items(Child pages) Macro and publish the page.
      3. Perform a space-level PDF export that includes the parent page and its child pages.
      4. Open the exported PDF and click on one of the child page links displayed within the Child Items(Child pages) Macro section.

      Expected Results

      Clicking a child page link in the Child Items(Child pages) Macro should navigate to the corresponding location within the same PDF file (intra-PDF link behavior), similar to manually inserted page links.

      Actual Results

      Clicking a child page link in the Child Items(Child pages) Macro opens the live Confluence Cloud page in the browser, not the destination within the PDF file.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

              0543480daccd Daisy Reyes
              9f3b28a42856 Kyungmin Kim
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: