I'm wondering what the difference is between a parent portal you add to a sub-domain from the host settings page, a child portal, and doing a full install on a sub-domain???

For instance, I know you can't back-up/re-install a child portal by itself - you have to do the parent portal and all child portals. Are there advantages to doing a full install vs. adding a parent portal to a sub-domain?

Thanks

Greg

You can use parent and child portals to make it easy for adding other portal sites. Physically there is no difference between parent and child. But you can change child portal structure by adding an alias like www.domain.com to make it parent portal.

Lets say you have a host portal installed at www.hostportal.com

Child: www.hostportal.com/child

Parent: www.hostportal.com/child2

               www.parentportal.com

It is easy to update their dnn versions when you have multiple portals at one hosting account.

But it is not easy to troubleshoot problems, because if host portal has an error about dnn, that error may effect all sub portals (including parent and childs)

I have www.mikroproje.com as host portal and www.mynetnuke.com as parent portal hosted by mikroproje.com DNN application.

I find it easy to use and manage under one dnn instance. But requirements are important. For example perfomance of portals.

Regards

you statements are correct. The only in-between solution is sharing a database using different objectQualifiers, but I learned from other users, who tried this with DNN 4.5.x, that there are issues with this configuration, I therefore do not recommend this solution.