Issue Details (XML | Word | Printable)

Key: GLIFFY-35
Type: Bug Bug
Status: Tested Tested
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Shannon Krebs
Reporter: Chris Kohlhardt
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Gliffy

HTML Export doesn't include gliffy diagrams

Created: 13/Nov/07 05:53 PM   Updated: 05/Mar/08 06:42 PM
Component/s: Confluence Plugin Integration
Affects Version/s: None
Fix Version/s: Gliffy Plugin for Confluence - 1.3.6
Security Level: Anyone may view


 Description  « Hide
Migrated from: http://developer.atlassian.com/jira/browse/GLFY-10

Gliffy diagrams are not included in the HTML export, which we use.

This issue depends on:
http://jira.atlassian.com/browse/CONF-7601

--History copied from old issue tracker--
Chris Kohlhardt - 13/Feb/07 11:25 AM
David, just to clarify, are you using the 'Export Space' feature in the Advanced tab within the Browse Space section?

David Ruddock - 29/Jun/07 11:09 AM
Hi Chris,
Are you using the 'Export Space' feature in the Advanced tab within the Browse Space section?

Yes.

Also I was excited to see that CONF-7601 has been fixed!

Hopefully this will do the trick - or are you expecting to have to do follow up work?

Cheers, David

Chris Kohlhardt - 29/Jun/07 11:13 AM
Once the release notes for Confluence 2.6 become available, we'll know what changes need to be made (if any) on our side to address this issue.
Thanks for following up!

-chris

David Ruddock - 02/Oct/07 09:22 AM
Hi Chris,
It would be great to know if this is fixed in 2.6 - which is now available.

Thanks, David

Chris Kohlhardt - 02/Oct/07 02:00 PM
David,
We'll be looking into this as a part of the next minor release for the plugin.

-chris

Chris Kohlhardt - 24/Oct/07 08:43 PM - edited
CONF-7601 has been re-opened. In theory, when CONF-7601 is fixed we wont need to do anything to fix this in Gliffy....



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Chris Kohlhardt added a comment - 28/Nov/07 05:45 PM - edited
Atlassian states that they have fixed this in both 2.6 and 2.7.

The 2.6 fix shouldn't require us to do anything.

The 2.7 fix:

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.

We need to fix this on our end so that HTML export will work in 2.6 AND 2.7.