Hi Everyone

Thanks for commenting on this issue. This does look to be a regression of this problem in Confluence 5.5.2. Rather than re-open this issue I've cloned this to a new issue: https://jira.atlassian.com/browse/CONF-33937 that we'll use to track the development and fix of this problem.

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian

I confirm that I have a regression in my installation of Confluence 5.5. Steps are exactly the same like described in CONF-26367

It works fine for On-Demand (5.5-OD-24-011).

Hi jfb

Thanks for getting in touch. Sorry to hear that this issue seems to be happening again for you. Would you be able to provide me with a list of steps that you're going through to reproduce this issue.

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian

shaffenden, jxie can you please check out if we re-introduced this problem?

Getting this bug in 5.4.4. Affects the LaTeX Math add-on.

I'm seeing this bug again in Confluence 5.5.2. I've tried inserting images, charts, and other macros, but none of the images turn up in the Word file. It looks like this issue needs to be reopened.

samjones looking at your support case, it seems more like you ran into the slightly different bug https://jira.atlassian.com/browse/CONF-26021, which does still exist in 5.2.3

Per CSP-108819, this bug is NOT fixed in 5.2.3

Total pita. I upgraded to 5.2.3 so I could be free of all the bugs we hit in 5.1.2....

But no.... gotta still live with em....

Normand and Hans Peter are completely correct.

Atlassian's attitude toward bug fixing is completely upside down and customer-hostile.

I upgraded from 4.1.x to 5.1 to get fixes to the editor, and instead got a show stopping horrible regression, and I can't go back to 4.1.

Horrible behavior by Atlassian.

(I am glad I am not Gliffy, forced to have my customers live with a breaking confluence environment.)

As it is too often the case with Atlassian, a lot of new bells and whistles are added with each release, but simple critical issues for end users, like this one are ignored.
Atlassian definitely need a product owner that goes to talk with customers and listen a little less to the developers who want to have fun developing new cool things!

The customer is the primary reason why you are there Atlassian, not the developers. They are there to provide added value to customers. No added value, no customers, no developers. The equation is very simple!

As this ticket is now used as the only open one to refer to several other related bugs, the developpers need to make sure to review all these referenced tickets, as they document different aspects of similiar problems.
It is not only Gliffy diagrams and output of plugins (like charts) which probably need to be executed on the fly while the word document is created. The word exporter does not even handle as simple cases as the standard Confluence built-in icons (emoticons), nor any other image file.

It should also be noted that the earlier tickets were reported since Confluence 2.x, with report dates in 2007! (6 years, and some of these tickets (including this one - one year old) are ranked "critical" ..... this creates once more doubts in me regarding the Confluence's prioritation and bug fixing process)

cross reference:

http://jira.gliffy.com/browse/GCONF-16

https://jira.atlassian.com/browse/CONF-26367

https://support.atlassian.com/browse/CSP-102740

I have been told that this bug is a dupe of:
https://jira.atlassian.com/browse/CONF-26367

This bug also affects 5.1.2 (that is where I see it), and the other versions noted on https://jira.atlassian.com/browse/CONF-26367

Yes, it impacts gliffy big time. Because of this bug, we lost critical, core confluence functionality when we moved from 4.1.x to 5.1.2. I am in the process of migrating a large document out of confluence+gliffy over to Word + Visio so I can do my daily job of maintaining a technical document that is published almost every week.

Given that CONF-26367 has been open for 9 months, and Confluence has had multiple releases in that time with the bug, I fear there is no reason to expect a quick fix.

Word+visio.... Back to the future. (Actually a huge PITA – I opened visio this week for the first time in a year)

Doesn't work with Diagramly. Images used within the diagram are not exported. As well not to PDF.

I have the problem even with attached images--not sure why or if it's even related, but just wanted to bring attention to it. Thanks!

Problems with Gliffy here too

Our users are being very vocal about this, https://marketplace.atlassian.com/plugins/com.mxgraph.confluence.plugins.diagramly (see reviews). Could at least a warning be displayed in meantime if such images exist so we don't have to continually answer support questions on this?

Currently can't get Gliffy and Balsamiq diagrams exported into word. Confluence version 4.3.2 build number 3391

Hello, we are also having a serious problem when exporting pages with Gliffy diagrams. This issue tracked at Gliffy's Jira http://jira.gliffy.com/browse/GCONF-16 stated, that it required https://jira.atlassian.com/browse/CONF-6246 to be fixed, but even fixing the CONF-6246 didn't help, so a Gliffy support engineer then pointed me to this issue. This bug really makes working with Gliffy and Word export very inconvenient.

+1 for Gliffy support needed

The single biggest issue preventing me from working "peacefully" with my customers who want/need finished documents in word format is this bug.

This is specifically true of Gliffy and Balsamiq mockups. Not being able to have these 2 plugins images exported to word essentially renders Export to Word useless to us.

The most critical plugin is an internal plugin that uses ExportDownloadResourceManager.getResourceWriter(). In addition, the images apparently get resized slightly when exporting to pdf, which makes for ugly text.

How soon can we expect this to be fixed?

The changes required to fix this problem are quite involved. The fix might even involve changing to the integration points for plugins that generate images and changing those plugins. Right now we are not working on this issue but depending on the demand (number of votes) we will consider scheduling the work.

Also, can you please comment with the list of affected plugins/macros you guys use the most?

Ah, thanks. How soon can we expect this to be fixed?