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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...many subportals in one foldermany subportals in one folder
Previous
 
Next
New Post
10/27/2006 10:50 AM
 

phixate wrote
Thanks IndianGuru and dstuve! I was having a hard time finding info on this. One last question. Do you need to install the DNN files separately into the child folder as well, and then just link to that folder? For instance, here are two ways I was thinking of doing it:

1. Parent portal: website.com/dnn       Child Portal: website.com/demo
In this method I installed separate files into the demo directory and ran the install from going to it on the web (website.com/demo). The parent was on DNN 4.3.2 and when I installed DNN 4.3.5 in the method described above, it upgraded the database. It's weird that it upgraded several times for me when browsing the site on a few occasions yesterday (probably due to my parent site being cached by Pageblaster). It seems fine now and everything works as planned. I don't want to speak too soon but I'll keep my fingers crossed.

2. Parent portal: website.com       Child Portal: website.com/demo
My hosting provider suggests that I don't install DNN on the root of my site, but rather to a sub directory. That's why I did the first method. Is it better to have the parent in the root and the child in a subdirectory?

Also, I was under the impression you didn't have to install the DNN files for each child portal after the parent is installed. Am I missing some thing, or do you need the separate default.aspx file to reference on the web.

Thanks so much for your input!

 

Correct you only need one installation for each portal, parent or child.   The only physical difference is the navigation folder that loads your site(the one that contains default.aspx) and the files folder that stores your sites files such as pdfs,.docs, images....

Edit, you only need one installation for all of your portals.  I wasnt clear, sorry.


DotNetNuke Search Engine
ASP.Net Search Engine
Email me to add your favorite sites to the search List.
 
New Post
10/27/2006 1:41 PM
 
So you need to upload ALL of the DNN files to the child subfolder AND the parent. Essentially there are two places you need to unzip all of the DNN files to. I was just making sure that you couldn't accomplish creating the child portal without installing the complete set of files separately for the child portal.

Why is there even a child option in the host login when creating a portal? It seems like a useless feature if you're just linking to a new set of DNN files. It's the same thing as linking to a different domain altogether.
 
New Post
10/27/2006 8:16 PM
 
OK I'm officially confused ;)  So it IS possible to do multiple portals with just one set of DNN files. Very cool. That's my main question. So when you create a new portal as a child, what goes into the subdirectory? And how is the linking handled with DNN to that child portal? With an alias? I tried putting the alias "website.com/dnn/demo" in the child portal settings but it didn't work. Is there a tab ID in the url that I need to use? If so how do I find it? And how do you add pages to your child portal? Do I create a separate admin-like access login for that portal then login with it to create pages? Oh so many questions, I know... I've got newbee written all over me.

If you're wondering, my site is phixate.com and I've been recommended to install my DNN files to a subdirectory (phixate.com/dnn). There's a redirect pointing it to the dnn directory. This would be much easier on my own server, but I'm on "Discount"ASP.NET. It would also be much easier if I could set it up with separate domains and databases... in an ideal world, but I'm not rich YET. So this is my pain! Arrggg. Thanks for enduring along with me!
 
New Post
10/28/2006 5:01 AM
 

phixate wrote
So you need to upload ALL of the DNN files to the child subfolder AND the parent. Essentially there are two places you need to unzip all of the DNN files to. I was just making sure that you couldn't accomplish creating the child portal without installing the complete set of files separately for the child portal.

Why is there even a child option in the host login when creating a portal? It seems like a useless feature if you're just linking to a new set of DNN files. It's the same thing as linking to a different domain altogether.

Parent portals are, mainly, for different Domains, while child portals can be created for children of those domains. You do NOT need to upload the files twice... in one install, DNN supports many parent and child portals. For supporting Child portals DNN has to create a folder for that child. within that folder is only one file, default.aspx which makes a redirection.

EG: parent1: www.mysite.com, parent2: www.site2.com

children: www.mysite.com/child1, www.mysite.com/child2, or www.mysite.com/myportals/child3, www.mysite.com/myportals/child3 where child1 and child2 are folders created on the web server; the same for myportas folder that contains the folders child3 and child4 - for these sub-child-portals watch the portal alias.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...many subportals in one foldermany subportals in one folder


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