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?
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs