Hello!

I have created one DNN 6.0 site and it's working just fine.  I'm looking at creating a second DNN site that is somewhat connected to the original portal.  Is there an advantage to the second site being a parent or child portal? From an admin/host standpoint, is there a difference between the two (when editing)? 

Thank you!

--Jim (jwornell@zetron.com)

Sibrabrata is partially correct. A Parent Portal needs a DNS record configured that points to the site. Also, the web host needs to allow you to configure multiple DNS names pointing to the same hosting package (some webhosts only allow one....some limit the amount that can point to your hosting package...while others allow unlimited). These limits (and additional DNS records) do NOT apply to child portals.

A Child Portal MIGHT have issues with the CKEditor (I've encountered this).

I always configure my new portals as Child Portals to start with. Once the site is ready to go "live", I create the DNS record and add the Portal Alias (effectively turning it into a Parent Portal).

You can also use Child Portals to have two separate portals appear to be part of the same site. For instance: www.mysite.com and www.mysite.com/secure could be 2 different DNN portals, but, based on the URLs, look like the same site.