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

XMLWordPrintable

    • 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.

            [CONFSERVER-6919] Macros and plugins should be able to render themselves properly for PDF and HTML export

            Matt Ryall added a comment -

            Confluence 3.0 brought significantly improved PDF export and there are also APIs available for plugins to determine to destination format at render time:

            • com.atlassian.renderer.RenderContext#getOutputType
            • com.atlassian.renderer.RenderContextOutputType

            We consider this issue resolved.

            If you have any problems with PDF or HTML export, please raise a new specific issue or vote on an existing one if it exists.

            Matt Ryall added a comment - Confluence 3.0 brought significantly improved PDF export and there are also APIs available for plugins to determine to destination format at render time: com.atlassian.renderer.RenderContext#getOutputType com.atlassian.renderer.RenderContextOutputType We consider this issue resolved. If you have any problems with PDF or HTML export, please raise a new specific issue or vote on an existing one if it exists.

            RyanA added a comment -

            This is fixed for PDF export but nothing has been done to address this issue in HTML export so I'm leaving this issue open for now.

            You can try it out by downloading the release candidate from http://www.atlassian.com/software/confluence/DevReleaseDownloads.jspa , and discuss the new pdf export with us at http://confluence.atlassian.com/display/CONF3BETA/Home. You can find some preliminary documentation on the new pdf export at http://confluence.atlassian.com/display/CONFEXT/Improved+PDF+Export+Documentation

            RyanA added a comment - This is fixed for PDF export but nothing has been done to address this issue in HTML export so I'm leaving this issue open for now. You can try it out by downloading the release candidate from http://www.atlassian.com/software/confluence/DevReleaseDownloads.jspa , and discuss the new pdf export with us at http://confluence.atlassian.com/display/CONF3BETA/Home . You can find some preliminary documentation on the new pdf export at http://confluence.atlassian.com/display/CONFEXT/Improved+PDF+Export+Documentation

            AudraA added a comment -

            We are looking at fixing CONF-2079 within this year, and it might resolve this issue as well.

            If you're interested to know how we decide on which features to implement, please read this:
            http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

            AudraA added a comment - We are looking at fixing CONF-2079 within this year, and it might resolve this issue as well. If you're interested to know how we decide on which features to implement, please read this: http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

            Agnes Ro added a comment -

            We are well aware of this problem, so there is no need to get all your users to vote

            Good news is, we are currently looking into a different PDF library that would help resolve this problem (for Confluence 3.0). HTML exports however may be another issue.

            Agnes.

            Agnes Ro added a comment - We are well aware of this problem, so there is no need to get all your users to vote Good news is, we are currently looking into a different PDF library that would help resolve this problem (for Confluence 3.0). HTML exports however may be another issue. Agnes.

            Andy Brook (Javahollic Software) added a comment -

            My users are starting to use more macros in pages, and are now hitting this. As company confluence advocate, its a little embarrassing that simple features break. I for one would trade new features for existing features working as users expect them to.

            Given this issue has not many votes, and has been open for some time, I just know its not going anwhere soon. If I got each of my users to vote (~800 last check), would that speed up addressing the problem?!

            Andy Brook (Javahollic Software) added a comment - My users are starting to use more macros in pages, and are now hitting this. As company confluence advocate, its a little embarrassing that simple features break. I for one would trade new features for existing features working as users expect them to. Given this issue has not many votes, and has been open for some time, I just know its not going anwhere soon. If I got each of my users to vote (~800 last check), would that speed up addressing the problem?!

            Dan Hardiker added a comment -

            This remains a problem: http://forums.atlassian.com/thread.jspa?forumID=101&threadID=29233

            Dan Hardiker added a comment - This remains a problem: http://forums.atlassian.com/thread.jspa?forumID=101&threadID=29233

            Hendrik Vermeiren added a comment -

            We use the ms visio viewer as a user macro.
            This displays fine, but the export to PDF misses the visio flow. See https://support.atlassian.com/browse/CSP-13435.
            Please vote for this!

            Hendrik Vermeiren added a comment - We use the ms visio viewer as a user macro. This displays fine, but the export to PDF misses the visio flow. See https://support.atlassian.com/browse/CSP-13435 . Please vote for this!

            Ankur Gupta added a comment -

            We were using PDF export as a means of taking confluence to those who don't want to come to it. The macros not working in the PDF export is a big disappointment.

            Ankur Gupta added a comment - We were using PDF export as a means of taking confluence to those who don't want to come to it. The macros not working in the PDF export is a big disappointment.

            Stefan Baader added a comment -

            Hello
            in our company's wiki we have the same problems exporting pdf.
            Confluence 2.2.9
            Stefan

            Stefan Baader added a comment - Hello in our company's wiki we have the same problems exporting pdf. Confluence 2.2.9 Stefan

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

                Created:
                Updated:
                Resolved: