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 ...Need to redirect from root (mysite.com) when dnn resides at mysite.com/dnnNeed to redirect from root (mysite.com) when dnn resides at mysite.com/dnn
Previous
 
Next
New Post
4/6/2006 10:42 AM
 

How about reassigning the root of my website to the mysite.com/dnn physical address?  Is that the answer?
Is that the standard way hosting services deal with this?

 

 

 
New Post
4/6/2006 5:28 PM
 
I dont believe that the creators of DNN expected that novice users would have to code. My host for example, all I have to do ...when I am ready... is to ask them to make my site live, they will then point my domain right to my DNN sub folder. It is a good practice to put your applications in sub directories off the root not only for organization but you may write something in the future that you only want a few people or customers to get to. It is much easier to control access at the folder level rather then having to sort through a bunch of project files to figure out what to set permissions on...

Anyways... see if your host will work with you and point right to your DNN sub folder it shouldn't be a problem.


Will
 
New Post
4/6/2006 6:56 PM
 

I had the exact same question.  I am a major newbie here, so the next question my seem a little stupid.  What does the proxy setting in the host account do?  Is this what this is for?  I am with godaddy and my site is also at mysite.com/dotnetnuke.  We are now ready to go public, and would love mysite.com.  I am not sure how cooperative godaddy is going to be because I asked them about this when we first started developing the site and they told me I would have to do the redirect.  Anyway, if they are not cooperative, we do have an alternate solution.  We will have what I believe what is called a splash page on the site editor we are using now and a message that says click the tree to enter our site (our logo is a tree). 

Thanks in advance for any info about the proxy settings!

Michelle

The site is at www.brazoshomeschoolers.org/dotnetnuke if anyone wants to have a look!

 
New Post
4/6/2006 10:09 PM
 
I am also running DNN on GoDaddy, and have a solution that may work... I have a whole (6-8 pages) HTML site built and uploaded to the main hosting area.  I only use a few modules of DNN for calendar, and forums.   I made the DNN calendar page the default DNN page from login, so users only go there.  I added links to my HTML pages to only the DNN forum page and the calendar page.  These are the only DNN pages visible to the users.  So to the users, it is almost transparent... they go to a static HTML homepage, link to a DNN forum page or DNN calendar page from there, with all links shown only pointing back to the html in the host root.

Would this work for you?
Is it a bad idea for me?

This is my first DNN foray, and I'm only guessing... any advice or warnings appreciated!

TerryD

Michelle - Your Site is very nice!
 
New Post
4/10/2006 4:30 AM
 

Actually, IIS is more at fault than DNN when it comes to child folders. The first issue is a virtual directory vs. a web application, the second issue is that web.config file(s) are additive from the root. A web application can have more than one web.config file, the settings in the root apply to all the child folders - the child web.config take precedence over the parent web.config file(s).

For example, if you manage to get DNN working on a child folder such as www.somedomain.com/test and you put an empty web.config file in the root, the DNN site will break. Remove or rename the empty web.config file and the site will work again.

Considering that web appliations in child folders may use different application pools or may be running side-by-side using ASP.NET 1.1 or 2.0, you can understand how complicated this can get.

Ideally DNN should be in the root of a web application to prevent headaches.


Dwayne J. Baldwin
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Need to redirect from root (mysite.com) when dnn resides at mysite.com/dnnNeed to redirect from root (mysite.com) when dnn resides at mysite.com/dnn


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