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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install into Hosting Provider scenarioInstall into Hosting Provider scenario
Previous
 
Next
New Post
1/3/2006 3:55 AM
 
These are two different questions than the one originally posted.
But here we go:
- skins: if the skins are installed at the host level (menu HOST -> SKINS) they will be available for all the portals on the same installation. If you want  a given skin to be available ONLY for a given portal you have to install it on the admin section (menu ADMIN -> SKINS)

- modules: you can define a module as "Premium" and then select which portals will be able to use that given module. But if the module is avaible on a given portal then the admin will have full access to it.


Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
1/3/2006 12:26 PM
 
Ok...I am beginning to understand how this all works. Let me go a little farther. I have an existing IIS 6 config with the following:
1. ASP.NET 2.0
2. over 100 hosted domains using Host Headers
3. Default website is Off
4. SQL Server 2000 (all patches)

Now I am not sure how I should setup the initial DNN Portal installation. Here are my two conclusions. Let me know which one will be best please:

1. Turn on Default Website and follow directions.
2. Set it up some other way.

My main concern is that I do not want to this to impact any of my existing customers current configurations. I would however, like to be able to migrate them to DNN if they so choose. If I understand correctly DNS for every domain that I am hosting that I want to have have DNN setups on will point to the same IP and then DNN will handle the DNS-to-Portal translation?

Sorry for all the questions and thank for the help so far.

Troy
 
New Post
1/3/2006 1:48 PM
 
Troy,
I'm not an IIS master so my explanation can be a bit vague but this is the idea:
you setup a domain (or as many domains as you need) on IIS to point to the same single folder where dnn is installed. If this is done correctly on the first call to this domain the default dnn portal will be created and it will "listen" to the domain used on that call (say www.xyz.com).

Then on the menu Host->Portals, you can create as many portals as you need. If you have other domains pointing to this same folder this is just a matter of enterting the correct (new) domain and other information and click create portal. Then a new portal will be created and it will be listening to this new domain (say www.abc.com).

This will not affect any of your other clients if you make the setup on IIS correcty.

Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
1/3/2006 4:04 PM
 
Ok. I have just setup all of the required installation parameters from the installation docs. Now when I browse to the DNN folder to have it start the install I get:

Line 4: <sectionGroup name="dotnetnuke"> Line 5: <!-- the requirePermission attribute will cause a syntax warning - please ignore - it is required for Medium Trust support--> Line 6: <section name="data" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/> Line 7: <section name="logging" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/> Line 8: <section name="scheduling" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

Now I see where it says to ignore these but I don't know how to ignore them when it stops the execution of the page...should I just comment them out or what? Also I am using a SQL 2000 Server setup should I still keep all those SQL Express strings and such?

Thanks again!
 
New Post
1/3/2006 5:03 PM
 

Thank you for your promt reply. So should i delete the host skins first and them install them in admin, will i loose any of the design if i do this??

Also With the default DNN skins and containers, how would i get rid of this from the selection for a client portal?

Thank you again...great answers

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install into Hosting Provider scenarioInstall into Hosting Provider scenario


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