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 

            Efim (Inactive) added a comment - The workaround to this problem is also mentioned on documentation pages below: https://confluence.atlassian.com/conf67/export-content-to-word-pdf-html-and-xml-945102533.html https://confluence.atlassian.com/conf67/recognized-system-properties-945103674.html  

            Efim (Inactive) added a comment - - edited

            Hello everyone,

            Sorry for not finding the resources to look at this issue until now. Basically in the comments of this issue two different problems are posted. Both of them are related to the export to Word:

            1. Images from restricted page are displaying as empty boxes
            2. If we export a big page, images look OK at the beginning of the page, but disappear at some point

            Let's look at each problem in more details below

            1. Empty images on restricted pages

            The issue of blank images on restricted pages was fixed in version 4.2 in this bug: https://jira.atlassian.com/browse/CONFSERVER-6246

            I was not able to reproduce this problem in a recent versions (6.6, 6.8). If someone suffers from this issue at the version above 4.2, please post the scenario in comments. It will help developers to reproduce and to fix the issue.

            2. When exporting big pages with a lot of images

            When a page with big number of images is exported to Word, only first 50 images are exported as expected and others look like empty boxes. This problem right now is present in all Confluence versions.

            Actually, this behaviour was implemented intentionally. Starting from version 5.2 there is a system property atlassian.confluence.export.word.max.embedded.images with the default value of 50. Confluence reads the value of this property during startup and never exports more than this amount of images. The reason for such limitation is the stability of the system. Right now the export is done in the same JVM with Confluence Web Application. As an example, if someone exports huge page with a lot of heavy images, loading all images into memory for exporting can potentially cause OutOfMemoryError for the whole system. To prevent this from occurring, the system property was introduced.

            Workaround

            If there is a need to export pages with more than 50 images, the property can be overridden for versions starting from 5.2. For example, this parameter can be added to JVM startup flags:

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

            The proper solution to this problem is to completely remove the images limit. But this can't be done until we evict exporting in the separate process. Before this is done, a workaround described above can be used.

            I am changing the issue title/description to the second problem here because the first problem can't be reproduced. The issue will be resolved when we remove the images limit from export completely.

             

            Efim (Inactive) added a comment - - edited Hello everyone, Sorry for not finding the resources to look at this issue until now. Basically in the comments of this issue two different problems are posted. Both of them are related to the export to Word: Images from restricted page are displaying as empty boxes If we export a big page, images look OK at the beginning of the page, but disappear at some point Let's look at each problem in more details below 1. Empty images on restricted pages The issue of blank images on restricted pages was fixed in version 4.2 in this bug: https://jira.atlassian.com/browse/CONFSERVER-6246 I was not able to reproduce this problem in a recent versions (6.6, 6.8). If someone suffers from this issue at the version above 4.2, please post the scenario in comments. It will help developers to reproduce and to fix the issue. 2. When exporting big pages with a lot of images When a page with big number of images is exported to Word, only first 50 images are exported as expected and others look like empty boxes. This problem right now is present in all Confluence versions. Actually, this behaviour was implemented intentionally. Starting from version 5.2 there is a system property atlassian.confluence.export.word.max.embedded.images with the default value of 50. Confluence reads the value of this property during startup and never exports more than this amount of images. The reason for such limitation is the stability of the system. Right now the export is done in the same JVM with Confluence Web Application. As an example, if someone exports huge page with a lot of heavy images, loading all images into memory for exporting can potentially cause OutOfMemoryError for the whole system. To prevent this from occurring, the system property was introduced. Workaround If there is a need to export pages with more than 50 images, the property can be overridden for versions starting from 5.2. For example, this parameter can be added to JVM startup flags: -Datlassian.confluence.export.word.max.embedded.images=100   The proper solution to this problem is to completely remove the images limit. But this can't be done until we evict exporting in the separate process. Before this is done, a workaround described above can be used. I am changing the issue title/description to the second problem here because the first problem can't be reproduced. The issue will be resolved when we remove the images limit from export completely.  

            +1

             

            It's sad that this issue doesn't get the deserved attention.

            Werner Michels added a comment - +1   It's sad that this issue doesn't get the deserved attention.

            KPSA added a comment -

            Could this one at least be assigned?

             

            KPSA added a comment - Could this one at least be assigned?  

            Daniel Gehriger added a comment - - edited

            Workaround:

            I wrote a Python script which lets you select a Word file exported from Confluence and then adds any missing images in that file after retrieving them from Confluence.

            • A single executable (Windows) of that file is available at Bitbucket.

             

             

            Daniel Gehriger added a comment - - edited Workaround: I wrote a Python script which lets you select a Word file exported from Confluence and then adds any missing images in that file after retrieving them from Confluence. A single executable (Windows) of that file is available at  Bitbucket . The source code is public .    

            +1

            Confluence Server 6.3.3

            I have a big Confluence page with 57 pictures. When I export it to Word there is 50 pictures and the last 7 are missing.

            Natalia Orlova added a comment - +1 Confluence Server 6.3.3 I have a big Confluence page with 57 pictures. When I export it to Word there is 50 pictures and the last 7 are missing.

            +1

            When I export a long Confluence page to Word, all works fine at the beginning of the file (images on a Confluence page and included from other Confluence pages). After a certain number of pages (around page 17/18) the images stop exporting... it is really infuriating!

            Am I reading correctly that the workaround is only for older versions?

            I'm using Confluence Server 6.0.2

            Rosalind BANWELL added a comment - +1 When I export a long Confluence page to Word, all works fine at the beginning of the file (images on a Confluence page and included from other Confluence pages). After a certain number of pages (around page 17/18) the images stop exporting... it is really infuriating! Am I reading correctly that the workaround is only for older versions? I'm using Confluence Server 6.0.2

            +1

            +1 also experiencing this issue. For us it is exporting 15% of the images to the Word doc but the remaining 85% are not displaying.

            Cloud Licensing added a comment - +1 also experiencing this issue. For us it is exporting 15% of the images to the Word doc but the remaining 85% are not displaying.

            TWC added a comment -

            This is a problem for us as well. Resolution would be great.

            TWC added a comment - This is a problem for us as well. Resolution would be great.

            KPSA added a comment -

            This is also happening on our site. Please fix!

            KPSA added a comment - This is also happening on our site. Please fix!

            Leon Roy added a comment -

            I'd like to add my voice to the clamour for this issue to be resolved. It really skewers our case to management that Confluence can replace Word for our internal documentation and user guides if this issue is still prevalent after so many years!

            Leon Roy added a comment - I'd like to add my voice to the clamour for this issue to be resolved. It really skewers our case to management that Confluence can replace Word for our internal documentation and user guides if this issue is still prevalent after so many years!

            sfelius added a comment -

            Can you please fix this issue? At the Atlassian Roadshow you were boasting about the collaboration possibilities of Confluence as opposed to Word and it's 'track changes' feature. But if we cannot export to Word including images (we need this to respond to a client RFP), all these collab features are useless.

            sfelius added a comment - Can you please fix this issue? At the Atlassian Roadshow you were boasting about the collaboration possibilities of Confluence as opposed to Word and it's 'track changes' feature. But if we cannot export to Word including images (we need this to respond to a client RFP), all these collab features are useless.

            I'm having this issue as well. I see the framework for the images, but they aren't showing up. Very frustrating.

            Ryan Whitney added a comment - I'm having this issue as well. I see the framework for the images, but they aren't showing up. Very frustrating.

            Hi nicholas.tsiroyiannis

            Thanks for getting in touch. This issue isn't on our immediate backlog. There are a number of more critical issues that we need to address before looking into issues such as this. As this issue does have a big impact on the functionality of the office connector I would expect that we'd start looking into this soon. Unfortunately I cannot give you a precise timeframe.

            Regards
            Steve Haffenden
            Confluence Bugmaster

            Steve Haffenden (Inactive) added a comment - Hi nicholas.tsiroyiannis Thanks for getting in touch. This issue isn't on our immediate backlog. There are a number of more critical issues that we need to address before looking into issues such as this. As this issue does have a big impact on the functionality of the office connector I would expect that we'd start looking into this soon. Unfortunately I cannot give you a precise timeframe. Regards Steve Haffenden Confluence Bugmaster

            Dear Oli,

            This is a severe limitation. The office connector does not work for mac users. This renders the current workarround unusable.

            Whilst we love maintaining our documentation in confluence, and its a major use case for its adoption in our organisation, not being able to take content offline is significant. We (and I'm sure many other enterprise software vendors) have to provide documentation offline as well. This is either because implementation teams need to tailor the content for a Client or because it needs to be printed hardcopy (yes, some organisations still print manuals!!!).

            I would appreciate some feedback to your product board and to us in terms of where in your roadmap will you be addressing this,

            With thanks and regards

            Nicholas Tsiroyiannis
            VP Product, CBX Software

            Nicholas Tsiroyiannis added a comment - Dear Oli, This is a severe limitation. The office connector does not work for mac users. This renders the current workarround unusable. Whilst we love maintaining our documentation in confluence, and its a major use case for its adoption in our organisation, not being able to take content offline is significant. We (and I'm sure many other enterprise software vendors) have to provide documentation offline as well. This is either because implementation teams need to tailor the content for a Client or because it needs to be printed hardcopy (yes, some organisations still print manuals!!!). I would appreciate some feedback to your product board and to us in terms of where in your roadmap will you be addressing this, With thanks and regards Nicholas Tsiroyiannis VP Product, CBX Software

            Hi kishore.srinivasan,

            Unfortunately I currently have no update on this issue. This is on our backlog but there are a number of higher priority issues that we need to address before this. As soon as we have an more information on this issue we'll update this ticket with details.

            Regards
            Olli Nevalainen
            Confluence Bugmaster
            Atlassian

            Olli Nevalainen added a comment - Hi kishore.srinivasan , Unfortunately I currently have no update on this issue. This is on our backlog but there are a number of higher priority issues that we need to address before this. As soon as we have an more information on this issue we'll update this ticket with details. Regards Olli Nevalainen Confluence Bugmaster Atlassian

            Hello Atlassian,

            May we know whether you've planned to fix this issue in any of the next releases or have a patch for the previous versions?

            Many Thanks,
            Kishore Srinivasan

            Kishore Srinivasan added a comment - Hello Atlassian, May we know whether you've planned to fix this issue in any of the next releases or have a patch for the previous versions? Many Thanks, Kishore Srinivasan

            Having same issue on 5.0.3

            Luca Tanieli added a comment - Having same issue on 5.0.3

            The workaround using the "Edit in Word" doesn't work on Confluence Cloud. That option is not available.

            Mauro Badii (Inactive) added a comment - The workaround using the "Edit in Word" doesn't work on Confluence Cloud. That option is not available.

            Leon Guan added a comment -

            Having same issue on 5.5, painful.

            Leon Guan added a comment - Having same issue on 5.5, painful.

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

                Created:
                Updated:
                Resolved: