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

Images produced by macro plugins like Gliffy are not generated into .doc or .html exports

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.6.2
    • 2.2.9
    • None
    • all

      In the Gliffy plugin, we generate images on the fly via our included servlet plugin.

      When exporting in .doc or .html formats, the diagram images are not picked up in the exported files.

      We were able to work around this issue with PDF export by checking for RenderContextOutputType.PDF. When RenderContextOutputType.PDF is being used, we have our macro point to the file system which seems to work.

            [CONFSERVER-7601] Images produced by macro plugins like Gliffy are not generated into .doc or .html exports

            Don Willis added a comment -

            Don Willis added a comment - The documentation Agnes mentions is http://confluence.atlassian.com/pages/viewpage.action?pageId=107185152

            Hi Tiffany, See the comment above – the plugin developers needs to implement some changes on their side as well to take advantage of this capability. You should contact the original developer of the latex plugin.

            Jonathan Nolen (Inactive) added a comment - Hi Tiffany, See the comment above – the plugin developers needs to implement some changes on their side as well to take advantage of this capability. You should contact the original developer of the latex plugin.

            Is this fix supposed to render LaTeX images created by the LaTeX plugin in Word as well (version 2.6.2)?

            That was my understanding, but I have now upgraded to v. 2.6.2 and I still don't get any LaTeX images in my Word docs.

            Thanks,
            Tiffany

            Tiffany Bartlett added a comment - Is this fix supposed to render LaTeX images created by the LaTeX plugin in Word as well (version 2.6.2)? That was my understanding, but I have now upgraded to v. 2.6.2 and I still don't get any LaTeX images in my Word docs. Thanks, Tiffany

            Agnes Ro added a comment -

            The patch for 2.6 is only a temporary fix and will no need any additional work from plugin developers.

            However, the fix for 2.7 will require plugin developers to use the new manager to write/store the macro image content. This manager will also be responsible for the retrieval of macro image content (for exports).
            I will try to write some documentation for plugin developers on this, once released.

            Agnes.

            Agnes Ro added a comment - The patch for 2.6 is only a temporary fix and will no need any additional work from plugin developers. However, the fix for 2.7 will require plugin developers to use the new manager to write/store the macro image content. This manager will also be responsible for the retrieval of macro image content (for exports). I will try to write some documentation for plugin developers on this, once released. Agnes.

            Will this fix require action on the part of plugin developers who are currently experiencing this bug?

            thanks

            -chrisk @ gliffy

            Chris Kohlhardt added a comment - Will this fix require action on the part of plugin developers who are currently experiencing this bug? thanks -chrisk @ gliffy

            Agnes Ro added a comment -

            This problem has been re-fixed for 2.6.2.

            2.7 will have the proper fix is being monitored in a separate issue, CONF-9896.

            Agnes Ro added a comment - This problem has been re-fixed for 2.6.2. 2.7 will have the proper fix is being monitored in a separate issue, CONF-9896 .

            Thanks for the update Matt. Please let me know if there is anything I can do to assist.

            -chris

            Chris Kohlhardt added a comment - Thanks for the update Matt. Please let me know if there is anything I can do to assist. -chris

            Reopening. There are a few serious bugs with this implementation, and it also doesn't seem to work as advertised in all situations.

            (To be fair, much of this is due to the fact that space export was made a long-running task at the same time. The operations causing the current bugs are fine if done on the same thread.)

            Matt Ryall added a comment - Reopening. There are a few serious bugs with this implementation, and it also doesn't seem to work as advertised in all situations. (To be fair, much of this is due to the fact that space export was made a long-running task at the same time. The operations causing the current bugs are fine if done on the same thread.)

            Chris, I'm not sure. I'm investigating the failures this caused at the moment (CONF-9659), so I'm not sure we won't have to roll this back and find a better solution.

            I'll reopen this issue until we can confirm that it is fixed for you.

            Matt Ryall added a comment - Chris, I'm not sure. I'm investigating the failures this caused at the moment ( CONF-9659 ), so I'm not sure we won't have to roll this back and find a better solution. I'll reopen this issue until we can confirm that it is fixed for you.

            Hi Tiffany,

            Thanks for the idea.

            Changing permissions isn't really an option for us. The Gliffy plugin which we've created has to play nice with any permission setup that a customer has in place. We certainly don't want to override their permissions.

            thanks though!

            -chris

            Chris Kohlhardt added a comment - Hi Tiffany, Thanks for the idea. Changing permissions isn't really an option for us. The Gliffy plugin which we've created has to play nice with any permission setup that a customer has in place. We certainly don't want to override their permissions. thanks though! -chris

              agnes@atlassian.com Agnes Ro
              20ba2becdb4c Chris Kohlhardt
              Affected customers:
              5 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: