#Copy space plugin for confluence update#
#Copy space plugin for confluence archive#
#Copy space plugin for confluence software#

There’s no need to make any changes to the diagram. The workaround is simple: Open the offending diagram in the Gliffy editor and then save it again. (I encountered 3 such diagrams when copying the Confluence documentation this week.) The solution The problem seems to happen for old diagrams only. If you like, you can take a look at the bug report too. Unfortunately, earlier versions of the Copy Space plugin don’t give such a useful error. The attachment’s size property does not match the attachement’s data size: Attachment: The content that could not be copied was titled. Here’s the text of the above error message:Īn error occurred while copying the space. Solving a problem with Confluence Copy Space and Gliffy plugins 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: AttachmentDataStreamSizeMismatchException: Attachment data stream contains a different number of bytes to the declared size of the attachment. …CopySpaceException: An error occurred while copying an attachment…. The log files show an error message something like this: The space copying procedure runs for a while and then stops. So last week I started the Copy Space plugin and hit a problem.

I’ve written about Gliffy in an earlier blog post too. We also use another plugin called Gliffy to draw and display awesome diagrams. (A by the way: Atlassian support does not cover the Copy Space plugin - but we use it.) I’ve written more about this procedure in an earlier blog post. We use the Copy Space plugin to copy the current documentation into a new space.

#Copy space plugin for confluence software#

For each major release of the software that we’re documenting, we create a separate space containing the documentation specific to that version. We write and publish our technical documentation on Confluence wiki, and we use wiki spaces as the mechanism for version control. You’ll need to do this for each diagram that triggers the error. In short: Open the offending diagram in the Gliffy editor and then save it again. It’s possible that you may hit the same problem next time you use the Confluence Copy Space plugin. I ran into a problem when the space copying procedure encountered a fairly old Gliffy diagram.

#Copy space plugin for confluence archive#

But, if it absolutely has to be done, I would first try it in TEST system.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.

#Copy space plugin for confluence update#

You'll then get a notification for every status update on the issue.Īll in all, I wouldn't recommend doing it, because Atlassian does not support any of the methods.

Please sign up at !default.jspa to watch, comment on or vote for this issue. We have an improvement request logged in our JIRA to support Copy Space plugin. The method with Copy Space plugin does not retain Scroll Versions information in the new space, but this add-on allows you to change the space key (though it is not supported by Atlassian). And you would have to do it if you want to change the space key. However, the XML import method is very unreliable, especially when you are making modification to the entire entities.xml file. In the article above, the method #2 retains all Scroll Versions information upon importing the space XML back to Confluence. Please back up your Confluence instance before trying! I would also recommend trying first in DEV or TEST environment before following the steps in production. All available (but not supported) methods to achieve space copying is described on this page. There is no straight forward or supported way for copying the space to an instance where another space is having the same space key.Ĭonfluence currently doesn't have a supported method of copying space or changing the space key.

Is there any way to retain the version, page history, and approvals when publishing to a new / versioned space? I have tried setting up the new space with a working version, and then republishing from authoring to publishing but I encounter the error 'It is currently not supported to publish to an existing space where Scroll Versions is enabled.' To get around this we have tried two methods of migrationĢ) Exporting the authoring space, importing it into the published server (with new key)īoth of these methods loose the page comments, page history, version, and workflow (draft, complete, rejected etc.) as well as viewport configuration. We currently use the following scroll plug-ins:Īs part of this move we will have spaces with duplicate space keys (one for authoring, one for publishing). We are migrating from a two server setup where spaces are authored in one server and published to another, to a single server setup where spaces are published from an authoring space to a publishing space.