Migrating a space with gliffy diagrams

[Jochen Suckfüll]

When I export a space to XML and import that space into another Confluence instance, the gliffy macros end up showing a "Gliffy Macro Error".

Both instances are Confluence Server 5.9.4 with Gliffy Add-on 6.9.1.

The page attachments show a file with the correct name that is referenced by the Gliffy macro configuration. Using the "Edit" link there yields an error in the Gliffy editor that says "The file was not able to load because it was not recognized as a valid Gliffy file. [...]"

We have moved several spaces with more than 200 Gliffy diagrams. Is there a bulk way to fix the display of those diagrams?

[Jochen Suckfüll · Accepted solution]

It turned out that the attachments have not been imported correctly for some of the spaces we imported from XML. I'll investigate further to see how to fix the attachments in general.

[Matt Merrill]

 Did you ever figure this out?  Curious, we may need to do the same thing.

[Jochen Suckfüll]

Yes.

The space export of the (non-personal) space A had included a personal space B in addition to the originally exported space.

That personal space B was already present on the destination instance of Confluence, therefore the import failed. That effect was that the space A that we intended to move was actually present, and the attachments were there as well, but their filenames (on disk) still had contained the old ids and were therefore not accessible.

The fix was to remove the personal space B from the destination instance prior to importing the XML export of space A.

[Matt Merrill]

Very helpful thank you.  It's very difficult to even find the answer to whether it's possible to migrate Gliphy diagrams in Confluence at all.  Hopefully this page helps!

[Sonya Spangelo]

Is there a way to fix it after you did the move?