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...Multiple Portals?Multiple Portals?
Previous
 
Next
New Post
5/27/2006 6:47 PM
 
Will this work for subdomains also? Can I setup a base site at abc.com - then set up subportals at site1.abc.com and site2.abc.com ?
 
New Post
5/27/2006 8:08 PM
 

I honestly have never tried it, but I really don't see why it would work.

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
5/27/2006 8:09 PM
 

Also checked out your website.  Looks good.  You guys aren't looking for a freelance/work from home programmer/database guy are you?  Just thought I check.

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
5/27/2006 9:06 PM
 

DotNetNuke is designed from the ground-up with the idea of virtualised portals. To support this each portal has a numeric ID so that when a request comes in we can detect which portal serves it. When you first install dotnetnuke, it picks up the address of the website (which will normally be your development environment [e.g. http://localhost/dotnetnuke] or the url of whatever your website is [e.g. www.mysite.com]). This becomes the primary portal (which gets an id of 0 in the portals table). After this you can add additional portals, either child portals or parent portals. The difference between a child and a parent portal is that a child portal is a subdirectory off the primary portal (e.g. localhost/dotnetnuke/newchildportal or www.mysite.com/newchildportal), whereas a parent portal is a fullyqualified domain name such as www.someothersite.com. As this is a completely different url to the primary portal, you need to add this as a host header entry in IIS.

Some people get confused as we also support portal aliasing, which is the ability to have one portal respond to requests from different address's. This allows you to have a portal (e.g. portal 0) that responds to requests for www.site1.com and www.site2.com, and have portal 1 respond to www.site3.com. A very common use of alias's is to setup a portal so it responds to both development and production requests e.g. when you setup your site in development it has a url of localhost/dotnetnuke, but when it's deployed to a liveserver, you need it to respond to www.livesite.com. To do this, add www.livesite.com as an alias whilst developing, as otherwise when you deploy it to production, it will not know what portal ID to respond to when a request for www.livesite.com is passed to it (note: this is not completely true anymore, as in recent versions of DNN we automatically fallback to portal 0 when we get a request we can't resolve, but it's a good idea to add it)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
6/27/2006 12:55 AM
 
I understand how multiple portals work, but is there built in functionality for a front end store where users can "purchase" portals? I've seen these sort of sites, but am not sure whether they are custom for that company or something I can easily implement.

Thanks
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Multiple Portals?Multiple Portals?


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