Hi All.

I have one Portal running right now in my DNN-5.1.4. Installation.

Now i need a second Portal which i wanted to be the new parent and the existing one then should be a child of this new one.

What has to be done with the "old" one to be a child of the newly created parent?

I have full access to my server as they are located in the room to my left. ;-) so any hardcore changes to DB or whatever won't be a problem.

Thanks in advance for any quick solution

Kai

Hi Sebastian.

Thanks so far, but i hang with point 5. Could you explain a little bit more deeply?

Second question: the old existing domainname, pointing to the old portal should then point to the new parent. the new child (former parent) then should be reachable as www.mydomain.com\baby

Editing the portal-aliases is enough then?

I still don't get it....

Good news: i'm testing on my notebook first running Vista and local installation and DB

I managed up to point 4 and i have two portals now:
0 is my original parent which should become child and is reachable under http://localhost/testA
1 is the new parent which should "hear" in the future to the main Domainname and is reachable under http://localhost/testB

On my production machine i have  the portal running "listening" to www.mydomain.com
The new parent portal should be reachable in the future under this domain and the old portal should be www.mydomain.com/child

I recognized that there is a folder for each childportal only with a default.aspx in it. But i don't know what i should edit here in which manner.