Developer forum

And why can the urls not be in the URL index?

If they are not in the index, what will happen is that you create a 4th website that is active - and then when you activate the 3rd one, that will flip all the urls of the 4th one.

Hmm yeah, thats a conundrum. 

I was told that this is the preffered way to start with a fresh Swift environment, because I would then be able to keep the AreadId of the original Swift site, and in that way would be able to use the deployment tool to sync up database changes when a new swift database version is published. In the example of Swift 2.0 to 2.1 for example that would allow me to copy over new Customer Center items with less manual work.

Is there another way that I could work like this, and still be able to get a url without suffix? 

If not I think I would just have to delete the original sites, an go back to the drawing board for getting new content :-)

Ok - you should not listen to all those stories...

I would just work with the site you get - then you can move new pages with deployment tool - or spend 10 mins setting them up. It is just a page with a row and a module...

If you create multiple websites and you do not want them to share URL index, in settings / system / web & http / friendly urls, you can set "Unique URL structure for each website" and then you will not share URLs across sites.

Hi all,

Just an observation regarding the possibility of merging a Swift 2 solution into an existing Swift 1 solution. If this is not relevant for this discussion, then just ignore me :)

Originally, when we reintroduced the deployment tool for DW10, there was an issue related to Swift content. The issue was that Swift 2 was built on Swift 1 content, of course with a lot of changes. That meant that areas, pages, paragraphs, and so on, had the same unique identifier, a GUID value that deployment tool uses to tell entifies apart -- it's not the same as the ids of the entities. That led to a frankenstein merge where you would have websites and pages that were half Swift 1 and half Swift 2. I believe that the identifiers on the Swift 2 database were changed, but it might be something to look into.

As long as the identifiers are different, it is possible to deploy a Swift 2 site into an existing Swift 1 site. It will produce new ids for the deployed entities, but the unique identifiers will stay the same so you can deploy updates (let's say Swift 2.0 vs. 2.1) as well.

- Jeppe