Dest already exists when Importing or adding from Blueprint

Support
3

Thanks Matt. I’ve had a little support from your team on this issue and have found a workaround for the blueprint/import issue. I am now able to create a fresh copy of a site using this workaround:

  1. Export the site on your Desktop,
  2. Extract the zip file that you’ve exported and there should be a file named local-site.json open this file with a text editor and inside there look for the following:

"path":"/Users/username/Local Sites/testname" (Please note your file might looks different than my example)

The only thing we want to change on this is the name of the site after the Local Sites/ path (for the example above I’m changing)

"path":"/Users/username/Local Sites/testname" to `“path”:“/Users/username/Local Sites/Writeadiffernetnamehere”`` (wirte 1 word with no spaces in the sitename)

Obvioulsy it’s not an ideal solution but it’s workign right now – hopefully it will help anyone else here. I’ve got my fingers crossed for either the addition of cloning to Local or a fix to this weird "dest already exists’ issue when creating a new site from a blueprint in the longer term.

Happy to provide the log, but how do you want that supplied?

Thanks.