Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Could not locate exportDescriptor.properties in the archive

I'm trying to create a new space from an exported space zip file. I'm following all the steps and I'm getting this error:

"Could not locate exportDescriptor.properties in the archive"

 

I changed the Key in both the XML and properties file from the archive, zipped the archive using Terminal since I'm on a Mac, but I still get this error.

 

If anyone know how to successfully export a space and create a new space via import space, please let me know.

 

Thanks,
Melissa

2 answers

0 votes
Daniel Eads Atlassian Team Jun 10, 2019

Hey Melissa,

I just tried this out real quick on macOS 10.14 to see what the zip utility was doing. I was successful in getting it to compress and upload:

zip -r import.zip ./

This was executed inside the unzipped folder. Trying at the higher directory and unzipping the file didn't work, because it zipped the folder (and not the contents of the folder). If the Confluence importer doesn't find the exportDescriptor.properties file at the root of the zip file (not in a folder), it will throw that error.

Hope that helps, but let me know if there's more to the error you're seeing if you've tried zipping from inside the folder!

Cheers,
Daniel

@Daniel Eads I am too trying to import the space with a .zip file but from UI and I get the same error.

image.png

Does the name of the zip file important here?

My unzipped folder structure is as shown in pic2image.png

I got it fixed. had to zip the 3 files such that export... file is at the root when unzipped..

Like # people like this
0 votes
Reinier I'm New Here Aug 18, 2020

Slightly related to this: I wanted to change the 'Created by' name of the space I wanted to import, but before I imported it into the new/other space. In case you're looking at doing this too, here are the steps I took:

1. Export the desired space from the source Confluence instance

2. Export a random space from the new/other destination space that contains the 'Created by' name that you want to apply to the import space

3. Unzip the source and destination exports and open to edit from both the file 'entities.xml' (make sure you can distinguish the source and destination files)

4. In the destination 'entities.xml' file, find & copy the object:

<object class="ConfluenceUserImpl" package="com.atlassian.confluence.user"><id name="key"><![CDATA[----hash----]]></id>
<property name="name"><![CDATA[destination_accountname@yourdomain.com]]></property><property name="lowerName"><![CDATA[destination_accountname@yourdomain.com]]></property><property name="atlassianAccountId"><![CDATA[----hash----]]></property>
</object>

5. Paste the copied object in the source 'entities.xml' file you're going to import (of course make sure that you have the correct keys, don't just plainly copy what is mentioned above in 4.)

6. In the source 'entities.xml' file, replace all the key nodes (<id name="key"><![CDATA[----hash----]]></id>) with the key belonging to the new 'Created by' owner. This is the hash that is mentioned between the above nodes: <id name="key"><![CDATA[----hash----]]></id>

7. Save your file. Once saved, zip the files from root level as Abhay Bhat mentioned above and import the zip into your new/other Confluence instance

8. Wait for Confluence to process your import.

9. You're done.

10. Check in the newly imported space in your other Confluence instance for the mentioning of the proper 'Created by' name

 

Suggestion: If you have text you'd also like to have replaced at the same time, you can edit this in the source XML too. With any viable text editor you can do a find & replace action to change the desired texts. Changing it at this stage will save you time compared to doing this once it is imported in Confluence.

 

Hope this helps!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Confluence

What do you think is the most *delightful* Confluence feature? Comment for a prize!

- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...

323 views 23 8
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you