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 ...creating a new parent portalcreating a new parent portal
Previous
 
Next
New Post
10/3/2008 11:58 AM
 

I wish to create a new portal from my DNN installation v. 04.05.05, but don't want it live yet.

How can I get around this?

website:
www.sypensions.org.uk (this is the site to be revamped and pointed to my DNN server - but I don't want to point it to DNN server until I have completed the site.)

I read somewhere that when adding a new portal in DNN host settings "it must already point correctly to your DNN install, otherwise the parent portal creation will fail..."

or perhaps this means - point to it in IIS - creating a virtual directory?


thanks,
mark

 
New Post
10/3/2008 6:10 PM
 

Mark,

I would suggest using a host header in IIS of the IP address of your web server. You can then use a portal alias with the same IP address to access your site. Whenever you'd like it to go live, you can change both the host header and portal alias to the name of your server.

Hope that helps,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
10/6/2008 10:08 AM
 

Thanks Ian,

I have tried to set up a host header in IIS, but still having problems.

My DNN installation is on a virtual directory called www.sypensions.org.uk/dnn (the first site is working ok), but I can't create another site.

When creating the host header - I can not right click on the name of the virtual directory (which is called dnn) - this is where my dotnetnuke installation points to.

I can only cretae a host header (in IIS 6) from right clicking on the level above (on sypensions.org.uk website).
New host Header called - 'development.sypensions.org.uk'

I then created a new alias also: 'development.sypensions.org.uk'

When I visit www.development.sypensions.org.uk - I get an error:
"430 Not found, Unable to resolve name"

I also tried development.sypensions.org.uk/dnn as an alias, but this does not work either.

 Any ideas?

regards,
mark.

 

 

 
New Post
10/6/2008 9:52 PM
 

It may be helpful to outline the basic (logical) workflow:

Domain (uses) -> DNS (which points to) -> Server (which has) -> IIS (which loads) -> Web Site (generally based on) -> Host Header

This travels the path through the domain to your web application (DotNetNuke instance).

Once your DotNetNuke instance is loaded, the portal alias table is queried to find out which portal it should load, based on the incoming request.

To get to the point though - you'll need to create a "new web site" in IIS (you can remove your virtual directory) that points to your application root (file system). You can then configure it to use the proper host header (make sure you don't have the host headers used on any other sites that you were playing with...).

Also on your new web site - make sure you have A) a default document (default.aspx) B) application created, "Scripts Only" enabled C) ASP.NET 2.0 selected

Let me know how it goes!

Take care,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
10/7/2008 12:06 PM
 

Thanks. I created a new website in IIS and checked for the 3 things mentioned above(default.aspx,asp.net2.0 etc).

I was still unable to connect to the new site.

I am thinking that the problem is due to our firewall perhaps? This mabe why I could only get DNN working in a subfolder of our internet in IIS.

The only way I could get a new site created was to create a new virtual directory in the same IIS subfolder as our original dotnetnuke site with the same path (not sure if this makes sense.)

I then created a new parent portal in DNN with the following address: www.sypensions.org.uk/development/ (our first DNN site was: www.sypensions.org.uk/dnn if you were thinking it looks like a child site).

I realise you advised against the 'virtual directory' method - but I couldn't get it working any other way. And if it works, is there any real problem with the way it has been set up - using virtual directories?

mark.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...creating a new parent portalcreating a new parent portal


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