Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Problems with child portals and consequences of not using themProblems with child portals and consequences of not using them
Previous
 
Next
New Post
11/27/2007 3:50 PM
 

As I understand it, if you use child portals (or any use of multiple portals in one DNN installation) you won't be able to move individual portals to another DNN installation. To me, that limits the use of child portals to those cases of logically-related portals and not for unrelated portals. Unrelated portals therefore seem to require a new DNN installation (and web host account if using a commercial web host) for each one, with the attendant cost and work involved configuring each new DNN installation with all the modules and skins etc.

Am I missing something here?

 
New Post
11/28/2007 3:16 AM
 

this is generally correct, but you can group low cost portals in an installation (providing Admin access to site owners only, which do not need to be related, as many as you can assign domains to your hosting account. Separate installations can use individual sets of modules and can be backed up and restored individually. It depends on your (and your clients) needs.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/30/2007 7:37 AM
 

Thanks very much, Sebastian. You seem to have been elected to answer my several recent questions. I want to make sure I understand what you said as it applies to my potential problem.

What I do now is to group low-cost low-activity portals in one DNN installation. The DNN installation itself on a shared web host. Each portal in that DNN installation is a separate "site" to the site owners; they don't even know about the other "sites" in that DNN installation. Each site owner has admin access to their site only. My problem would be if a site owner decides they want to take their site and host it elsewhere. I have no way to split their site off and put it into another DNN installation. The same problem would arise if one of those sites got very popular and needed its own DNN installation or its own dedicated server. What would I do in one of those cases?

Sebastian Leupold wrote
this is generally correct, but you can group low cost portals in an installation (providing Admin access to site owners only, which do not need to be related, as many as you can assign domains to your hosting account. Separate installations can use individual sets of modules and can be backed up and restored individually. It depends on your (and your clients) needs.

 
New Post
12/2/2007 12:28 AM
 

Mick

You can certainly create a new instance of a portal when it's outgrown it's initial environment.

I have a couple of portals that have about 80 or so installs - when a site has outgrown or requires it's own build - it's easy -

You can choose to export the whole site and rebuild on new or you can simply create a new instance of the exact site and remove all the portals that are not needed. There is absolutely nothing wrong with doing this.  You can the apply the necessary upgrades to the invidivual portal and extend it as required.  I've been working with DNN since 2002, and have found this solution has worked for me.

I hope this gives you a further understanding to you question.

Nina Meiers
Lots of Free Skins

 


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
12/2/2007 10:21 AM
 

Nina, thank you very much for that reply. I'm not clear about what you mean, so...

>You can choose to export the whole site and rebuild on new<

Export the whole DNN installation? What is "rebuild on new"?

>you can simply create a new instance of the exact site and remove all the portals that are not needed.<

What is "create a new instance of the exact site"?

 

Nina Meiers wrote

Mick

You can certainly create a new instance of a portal when it's outgrown it's initial environment.

I have a couple of portals that have about 80 or so installs - when a site has outgrown or requires it's own build - it's easy -

You can choose to export the whole site and rebuild on new or you can simply create a new instance of the exact site and remove all the portals that are not needed. There is absolutely nothing wrong with doing this.  You can the apply the necessary upgrades to the invidivual portal and extend it as required.  I've been working with DNN since 2002, and have found this solution has worked for me.

I hope this gives you a further understanding to you question.

Nina Meiers
Lots of Free Skins

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Problems with child portals and consequences of not using themProblems with child portals and consequences of not using them


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out