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 help pointing to the Virtual DirectoryNeed help pointing to the Virtual Directory
Previous
 
Next
New Post
1/17/2007 9:18 PM
 
I think a few of you hard-core guys have missed the issue entirely :-) But hey, thats just my theory ...

We newbees read the documentations, the installation instructions, and the help pages. We then follow the directions these sources of information give us. The installation procedure states that DotNetNuke should be installed as a virtual directory under the default website (for instance "DotNetNuke_2" or "DNN"). This is fine, and it works great. When you browse to "http://www.mywebpagestuff.org/DotNetNuke_2" or whatever address you might have.

But what if the newbee installer didn't want his site to be a virtual directory? What if he wanted the DotNetNuke site to be the ONLY accessible content on the server? Browsing to the default website of the server will most likely return the default IIS "under construction"page - which was probably not what the newbee intended when he started installing DotNetNuke?

As I understand the question, he is wondering why he has a virtual directory at all, and what to do with the IIS configuration in order to get the DotNetNuke portal to be the only content returned returned from the website when navigating to its root. I had the exact same problem (but solved it in another manner) so I can certainly relate to the problem.

Why is DNN installed in a virtual directory in the first place? Why is it not installed in the root of a (new?) website? And what is the "best practice method" for solving this issue after installing a fresh DotNetNuke portal on a server dedicated only to the DotNetNuke portal?

:-)

- Jesper
 
New Post
1/18/2007 1:06 PM
 
I agree completely.

I read the online help first.  Some modules have downloadable Getting Started or other help and I read that too.  Then I'll search the forums.  If the search works, I'll read through numerous posts looking for the answer.

Many times I am trying to do something the help does not describe.  Other times I am trying to do something the help does describe, but either DNN core or the module no longer supports.  At this point, I wonder if DNN would be better without any documentation, rather than old documentation that is no longer useful.

A recent example is I was trying to set the default folder for Forum Attachments to go to.  Both the help and several forum posts gave the same instructions, but I simply could not find the referenced options in my DNN.  When I asked about it in the forum, I was told that the feature was no longer supported.  When I asked for it to be added back, I was told that it probably wouldn't happen.

I understand that DNN developers are volunteers.  I'm interested in helping out with a couple of the modules, but so far the attitude of this community has held me back.  If I'm going to contribute, I want to be involved with others who are helpful, not defensive.  DNN is a great product and it has grown beyond a learning tool for developers.  It is now being marketed to the general public as a solution for commercial web sites.  But if you're not an experienced DNN developer, good luck getting your site running and functioning as you want.

I'll step down from my soapbox now.  Hopefully my criticism will be helpful and not counterproductive.
 
New Post
1/30/2007 6:30 PM
 
How about it guys? Any answers from the professionals who work commercially with DNN?

What is the answer to the "vurtial directory question"? I have a hack on my servers that works, but its not really a pretty solution.

When following the installation guidelines, DNN is installed into a virtual directory in IIS, named "DNN" or "DotNetNuke" or something along those lines. Why is the default installation made into a virtual directory rather than the main website, and what is the best or most official way of directing traffic from the root of the server to the DNN portal installed in a virtual directory?

In other words:

The guidelines tell me to install DNN in a location like "www.myfictivesite.com/dnn4". I have done that, and it works great. Now what? I want the traffic to hit the root, "www.myfictivesite.com" and not the /dnn4 directory?

Any answer would be appreciated - we cant possible be the only 3 guys wondering what to do about this ... ?

- Jesper
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Need help pointing to the Virtual DirectoryNeed help pointing to the Virtual Directory


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