-
Bug
-
Resolution: Low Engagement
-
Medium
-
None
-
5.3, 5.4.1, 5.4.2
-
Severity 2 - Major
-
1
-
This happens when importing a zipped xml file from one confluence instance to another.
*The creator and the importer are not the same user.
[CONFSERVER-32186] When importing a Space with confluence2.importSpace, the imported space doesn't show up in the Space Directory.
This bug is still present in 5.8+.
A workaround consists in re-indexing the Confluence database, but for large servers, this really is a problem.
Moreover, the problem affects search features on the Confluence interface.
Hi Frederick
Thanks for the update. The information you've provided is really useful.
Regards
Steve Haffenden
Confluence Bugmaster
Atlassian
Hi Steve,
Just so you know, this bug is still present in 5.4.1.
Thanks,
Frederick Plante
Hi Steve,
First of all, thanks for the quick response. Here are the informations you require.
This is the process we used to export the space. In the space, there's a space tools menu on the bottom left side of the screen. Then, selecting content tools, there's an export tab. That's what we used to create the xml file.
The exporter is in the confluence-admin group and so is the importer.
The steps required to reproduce this issue are simple. Using the exported xml file, make a call in xml-rpc like so :
confluence2.login(username, password);
confluence2.importSpace(token, byte[] zippedXmlFile);
confluence2.logout();
Thanks,
Frederick Plante
Hi Frederick
Thanks for raising this issue. Could you provide the steps required to reproduce this issue. I'm specifically interested in the process you used for exporting the space. Which version of Confluence was this. What privileges did the user exporting have and how do these differ from the importer.
Regards
Steve Haffenden
Confluence Bugmaster
Atlassian
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center