I`ve made test today on customer account and I have a problem with export at all. Export stopped on 50 % like on attached prtscr.
Maybe I should submit a new thread ?

Hi everyone,

We have increased the number of images that can be present on a page to 250. This is now rolled out across all of production. Please let us know if you experience any issues with this new limit.

Thanks,
Tyler

Is that something going on with this topic?
Its very uncomfortable for our customers to don`t have images aboove 50 in PDF.

I have this same problem with our Cloud version. 

A fix for this issue has been applied to Server and Data center (CONFSERVER-34211). Will this be coming to Cloud?

Hi everyone,

This is Sunny from the Confluence team. Thank you for raising this bug to our attention that there is a limit of 50 images displayed in page exports to Word. To set the right expectations, we may not be investing in changes to page exports in word in the short term. As a workaround, you can split up the page to two pages to offset the current limit of 50 images. As we work through other items on our public roadmap we will provide an update on this bug if we are able to work on a fix. Thank you again for your patience and the feedback you've provided on this bug.

Thank you,

Sunny

Understood. I will keep you updated along the way while making progress.

I'm not sure about open to the public, but I reported the issue and my name got attached to it through whoever logged it, so I appreciate being in the loop on it.

Hi kristopher.moran , I wasn't aware that Jira ticket is open to the public. Too much technical details, My bad. 

Btw, I have located the issue, I will bring it to the team to discuss the possible solutions. Stay tuned

I also agree the implementing Export to Word correctly is the right way to go about resolving this issue. It would also be great if you could figure out a way to not only implement the Export to Word correctly, but if you set it up so that we could export a whole, or part of a tree, through a few clicks. 

At our company, we would prefer it be set to unlimited, so that it does not require us to create multiple Includes pages to Export content. As for the technical issues around that, I'm sure we can count on Atlassian to sort that out. 

It also Affects to version 6.0.1.

Has any progress been made on this bug? It looks unassigned. How long will this status remain?

This has severely impacted our organization, as we have selected Confluence as the leading-edge single-source of record for our documentation. 

The Export to Word function is single-page, so we found this workaround on Stack Overflow:

1. Create a new wiki page
2. Use the {include} macro to pull content in from several pages one at a time
3. Tools > Export to Word

http://stackoverflow.com/questions/26226570/confluence-multiple-page-export-to-word

Unfortunately, there is a limit to how many images will be generated before errors occur, so this requires:

1. Create a large page and then go into the Word doc and replace all of the non-generated images with the images.
2. Create a number of small Includes docs based on where it looks like the big doc failed.
   • This requires an extra effort, as you create one small doc, generate it, and then discover that it throws an error at a certain point
   • So then you create another smaller doc based off of that error point, and then find the new error
   • You repeat the steps until you have a series of small docs with no errors
3. Then you have to combine those docs into a single doc and format that single doc

While all of us who have voted on this feature are aware that there is an Export to Word plugin, it is frustrating to see that there is a perfectly good Export to Word function in Confluence, but there is no way to Export a Tree and we depend on two layers of workarounds just to get it to work properly.

The Export to Word function makes better business sense (in either wiki or documentation mode, depending on the user) if it works properly for exporting pages with many images AND you can export a page tree.

Reopening this because it has had a fair amount of customer interaction since it was closed. This will allow voting and watching etc on the ticket, so we can better assess the impact.

Please vote on and watch the ticket if you are affected by this issue, and you will be notified of any updates. It still may not be high enough priority to make it onto the backlog, but this will allow us to better categorise it.

We are using Confluence for documentation as well and exporting to word is necessary for some users. This is an unfortunate limitation of the application.

Well, same here for us. Also our company (working in the engineering area on a global level) uses confluence for documentation. Sometimes a PDF export isn't the final solution since for exports for some special customers/projects a minor post processing of the content is necessary - and this is done within Word.
Now the workaround using two pages instead of one is indeed a feasible solution - BUT: you aren't always counting the images, are you?

When exporting a page to word images don't display after 50. This is a major problem for our company as we (like most others looking for the same solution) are documenting software and rely heavily on the use of screenshots and images. This was raised originally in 2013 but has been closed as of yesterday. Please re-look at this issue.
Regards,

Issue re-raised by nikki1: CONF-38997

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on bugs with a higher impact, and more votes.

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.

I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If demand for this picks up, we will reopen the issue.

This is certainly not a minor issue and should be upgraded and looked at asap. Does Atlassian have any date that this will be looked at? One of the major let downs imho of Atlassian is the huuuuuggggeeeee delay at times in fixing issues that affect many/all of your customers.

Thanks

I attached a link to issue CONF-35525.
That one describes the issues we ran into when trying HTML export as a "workaround" for this bug. It can hardly count as a workaround ... Two people have already wasted 10hrs of working time running from one bug into the next one. (Frustration is high ...)

I raised a support ticket (CSP-134046) for this yesterday before finding this to be a known bug today. (Still existing in Confluence 5.6.3.)

Priority minor: Sorry, but this must be a joke...
Export to some word processing software is imho a core functionality of any wiki, and this is broken. When documenting a software (with screenshots, icons etc.) pages containing more then 50 images are not an exception but the normal case. In our case it will mean that we are in trouble fulfilling a software documentation contract which requires to create editable Word documents for wiki pages containing literally several hundreds of images.

Any clue how we are supposed to achieve this if Word export is not working as advertised?

HTML export works (in principle), but

1. it does not cope with images containing a '#' in the file name. Well, we could resolve this by renaming those images.
2. if the resulting HTML page (containing several tables) is imported into MS Word it results in HTML tables on the page instead of "normal" Word tables. Those HTML tables are awkward to handle and cannot be formatted the way normal Word tables can.
   So this is not a real workaround.

Hi stefan.schulte@viega.de

Thanks for getting in touch and raising this issue. This is still on our backlog. Unfortunately there are a number of other, higher priority issues that we need to address before looking into this. As soon as we have any further information we'll update this ticket with details.

Regards
Steve Haffenden
Confluence Bugmaster

Anyone? please?

Also, as you defined the ticket priority minor (where easy workaround is available), care to elaborate the workaround in this case?

This is precisely our issue aswell. I just counted the images, and it's a hard cut after 50 images on our word exports that would contain more images.