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

Macros and plugins should be able to render themselves properly for PDF and HTML export



    • 8
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      At the moment, macros and other plugins that generate content are aware of their render mode but don't have the facilities to correctly render themselves for the destination format. The following things are often broken in the export of macros:

      • links, especially to Confluence content
      • images
      • styles and complex markup

      To fix this, macro plugins need access to a link/image URL generator for Confluence content.*

      A better API that indicates which render modes are required would also help. The current method of relying on the author to check a field in the RenderContext means that the export render modes are often forgotten.

      This issue incorporates specific instances of this problem.

      • There is actually a linkRenderer in the renderContext already. But to use it means creating a Link object, which itself requires a GenericLinkParser, a Manager and the object to be linked to. Not the easiest interface to work with.


        Issue Links



              matt@atlassian.com Matt Ryall
              matt@atlassian.com Matt Ryall
              35 Vote for this issue
              18 Start watching this issue