Solving a problem with the Confluence Copy Space and Gliffy plugins
Last week I used the Copy Space plugin to create an archive of the Confluence 3.1 documentation, because we’ll be releasing Confluence 3.2 very soon. I ran into a problem when the space copying procedure encountered a fairly old Gliffy diagram. It’s possible that you may hit the same problem next time you use the Confluence Copy Space plugin. Here’s the workaround.
In short: Open the offending diagram in the Gliffy editor and then save it again. There’s no need to make any changes. Start the space copying procedure again. You’ll need to do this for each diagram that triggers the error.
A bit of background
We write and publish our technical documentation on Confluence wiki, and we use wiki spaces as the mechanism for version control. For each major release of the software that we’re documenting, we create a separate space containing the documentation specific to that version. We use the Copy Space plugin to copy the current documentation into a new space. I’ve written more about this procedure in an earlier blog post. (A by the way: Atlassian support does not cover the Copy Space plugin — but we use it.)
So last week I started the Copy Space plugin and hit a problem.
The space copying procedure runs for a while and then stops. The log files show an error message something like this:
…CopySpaceException: An error occurred while copying an attachment…. AttachmentDataStreamSizeMismatchException: Attachment data stream contains a different number of bytes to the declared size of the attachment.
If you have the very latest version of the Copy Space plugin, you will see a nice neat error message on the screen, including a link to the offending diagram:
Here’s the text of the above error message:
An error occurred while copying the space. The copy was cancelled.
The content that could not be copied was titled: <Gliffy image name>. link
The attachment’s size property does not match the attachement’s data size: Attachment: <Gliffy image name, version, attachment ID and author’s username>
Unfortunately, earlier versions of the Copy Space plugin don’t give such a useful error.
If you like, you can take a look at the bug report too.
The problem seems to happen for old diagrams only. (I encountered 3 such diagrams when copying the Confluence documentation this week.)
The workaround is simple: Open the offending diagram in the Gliffy editor and then save it again. There’s no need to make any changes to the diagram. If you have the latest version of the Copy Space plugin (version 1.2) the error even includes a link to the offending Gliffy diagram.
Start the space copying procedure again.
You’ll need to do this for each diagram that triggers the error.
I’m using these versions of the software:
- Confluence 3.2-rc1 (release candidate 1)
- Copy Space plugin 1.2
- Gliffy plugin 2.0.2-RC2
Posted on 21 March 2010, in Confluence, technical writing and tagged Confluence, Copy Space, documentation, error, gliffy, plugin, technical documentation, technical writing, wiki, wikis. Bookmark the permalink. Leave a comment.