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

If a page with big number of images Exported to Word, some images are invisible

      The fix for this bug will be backported to our current Long Term Support releases if it passes our risk assessment.

      We recognise the impact of this bug and plan to backport the fix to our Long Term Support releases. Once the exact fix version is known we will update this ticket. Not all code changes are suitable to be backported and this may still be rejected during our review process.

      If a page contains more than 50 images, Exporting to Word will create a document with only 50 first images. All extra images will appear as empty boxes.

      The number of images for exporting to Word is controlled by the system property atlassian.confluence.export.word.max.embedded.images.

      The reason for the existence of such property is the stability of the system. Exporting is done in the same system process as the whole web application, therefore it is vital to limit the amount of memory consumed by the export.

      Workaround

      Before proper fix is done, on versions above 5.2 it is possible to override system property with other value: 

      -Datlassian.confluence.export.word.max.embedded.images=100

            [CONFSERVER-34211] If a page with big number of images Exported to Word, some images are invisible

            A fix for this issue is available in Confluence Server and Data Center 7.20.2.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            odykovy (Inactive) added a comment - A fix for this issue is available in Confluence Server and Data Center 7.20.2. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Hi @Nirav Patel, how can you export at least 50 images? I can't get confluence to export even 1

            Diego Alexander Vargas Atara added a comment - Hi @Nirav Patel, how can you export at least 50 images? I can't get confluence to export even 1

            Nirav Patel added a comment - - edited

            I am Confluence Cloud and have just faced this issue of word export ignoring all images after first 50.

            Writing a user manual and among other bugs I have found, this is the worst one so far. Have more than 50 images and when exporting to Word, first 50 shows up. Rest are missing.

            Is there a config that I can use to change this setting?

            I genuinely can't believe the Atlassian mindset here! Bugs are just left open for years without fixes!!!  

            Nirav Patel added a comment - - edited I am Confluence Cloud and have just faced this issue of word export ignoring all images after first 50. Writing a user manual and among other bugs I have found, this is the worst one so far. Have more than 50 images and when exporting to Word, first 50 shows up. Rest are missing. Is there a config that I can use to change this setting? I genuinely can't believe the Atlassian mindset here! Bugs are just left open for years without fixes!!!  

            Bak(x)l*ma₩*

            Anatoly Chirkov added a comment - Bak(x)l*ma₩*

            C'mon guys. Cut them some slack. They are busy you know.

            Ben van Gompel added a comment - C'mon guys. Cut them some slack. They are busy you know.

            So, you want to "gauge how pervasive the problem is"? This is quite simple: This bug renders the export to Word to NOT SERIOUSLY USEABLE.

            We intended to use the exporter feature to have a comfortable way to create a handout for our customers from the documentations, but with bugs like this we can't be sure that everything is included.

            Sorry to say, but: Not fixing such bugs is not enterprise software.

            Christian Keck added a comment - So, you want to "gauge how pervasive the problem is"? This is quite simple: This bug renders the export to Word to NOT SERIOUSLY USEABLE. We intended to use the exporter feature to have a comfortable way to create a handout for our customers from the documentations, but with bugs like this we can't be sure that everything is included. Sorry to say, but: Not fixing such bugs is not enterprise software.

            Please, fix it

            Gonchik Tsymzhitov added a comment - Please, fix it

            Really... Gathering Impact? For YEARS? 

            This is a "Bug".  BUGS = BAD.  BAD = BROKEN.  BROKEN should be FIXED.

             


            It's a tragic, but all to common, Atlassian story.
             
            Once upon a time a sincere user hopes to find a feature that really should be part of core functionality (as it is in one product but not another.) They search Atlassian's site and find a Jira ticket. They read that it is being reviewed. They are hopeful. They vote. They watch the issue. And, then...

            The hopeful user finds out the issue is either canceled, or not supported, or swept under the rug, or told there's not enough interest (because the requests are so utterly fragmented and we can't vote with one voice) or the ticket is left open for years. Yes, it is a sad, but all to common ending, to another Atlassian story.

            The End

            Oh, Atlassian. How I wish, wish, wish things were different.  PLEASE re-write the ending to this story (and others)!  Please fix the Bugs. Fix them with expeditiously. Please.

             

            Mark B Wager added a comment - Really... Gathering Impact? For YEARS?  This is a "Bug".  BUGS = BAD.  BAD = BROKEN.  BROKEN should be FIXED.   It's a tragic, but all to common, Atlassian story.   Once upon a time a sincere user hopes to find a feature that really should be part of core functionality (as it is in one product but not another.) They search Atlassian's site and find a Jira ticket. They read that it is being reviewed. They are hopeful. They vote. They watch the issue. And, then... The hopeful user finds out the issue is either canceled, or not supported, or swept under the rug, or told there's not enough interest (because the requests are so utterly fragmented and we can't vote with one voice) or the ticket is left open for years. Yes, it is a sad, but all to common ending, to another Atlassian story. The End Oh, Atlassian. How I wish, wish, wish things were different.  PLEASE re-write the ending to this story (and others)!  Please fix the Bugs. Fix them with expeditiously. Please.  

            Marco Centin added a comment - - edited

            If this ticket was really created in 2014, now I am really scared about using Confluence in a reliable way. I guess that I will have to revert to simple management of Word files for documentation purposes!

            Marco Centin added a comment - - edited If this ticket was really created in 2014, now I am really scared about using Confluence in a reliable way. I guess that I will have to revert to simple management of Word files for documentation purposes!

            frustrated 

            Abdelhalim ELKHATTABI added a comment - frustrated 

              5339cdd01cf4 Jeffery Xie
              8d92d19feb5e Jeremy Higgs
              Affected customers:
              93 This affects my team
              Watchers:
              81 Start watching this issue

                Created:
                Updated:
                Resolved: