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 ...Testing new DNN Community version  -  relative links don't workTesting new DNN Community version - relative links don't work
Previous
 
Next
New Post
4/2/2013 8:43 PM
 

Hi, this may be a dumb question but I'm trying to figure it out.

I've downloaded and installed the latest DNN Community and  replicated the database on a test database server with DNN itself installed on my windows 7 computer for testing purposes. Pointed to the test database server and things are working.

I have the installation at inetpub/MyWebsiteName/  (MyWebsiteName is the name of the application in IIS.)  So I can browse the site's homepage (default) by going to http://localhost/MyWebsiteName/  , So far so good.

 However, relative links are broken, When I click on a relative link, it leaves out the MyWebsiteName portion of the address and just serves the page from the inetpub/ level.

 Any ideas on what I'm missing here?

 Thanks

Tom

 
New Post
4/3/2013 6:45 AM
 

Since you are running on windows 7 you would be far betting setting up your test sites in their OWN root directories.  The old virtual folder approach is really a left over from the time with windows didnt allow you to host multiple sites on the same server.

For example - we setup a /wwwSiteName/website/ for every site we develop.
We then point IIS to the /wwwSiteName/website/ folder as its root.
Then you setup local bindings to complete the task
 - in most cases we set the hosting binding in IIS to http://www.sitename.local/

Finally a simple edit to the HOSTS file on your computer to point to that domain locally

open C:\Windows\System32\Drivers\etc\hosts as administrator  
Add an entry for your local domain
 127.0.0.1       sitename.local

Now you can browse to your local site using www.sitename.local - without worrying about all that legacy sub folder stuff.

Westa

 
New Post
4/3/2013 3:41 PM
 
Thanks Westa. This method is new to me so I've a few questions to clarify:

I'm not actually using a Virtual Directory, MyWebsiteName is an Application inside Default Web Site in IIS. The path is C:\inetput\wwwroot\MyWebsiteName\ (which I wrote incorrectly in my previous message). Are you saying I should move the DNN installation to outside the wwwroot/ folder? Or can I just create a new website in IIS and point it to the MyWebsiteName folder where it currently is?

Also, I have several Portals in my DNN, which are for different websites running on different domains. Would I set up those as separate websites as well?

thanks

Tom



 
New Post
4/3/2013 6:10 PM
 
Yes ... I would setup each site in its own hosting if the actual sites are in their own hostings of course.

And yes you do not want to put these inside wwwroot ... They can be seperate folders inside inetpub or anywhere else on you computer .... Just make sure you setup permissions for the folder to allow the asp user full rights ... Or if its your own secure computer ... You can just easily grant Everyone full rights

westa
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Testing new DNN Community version  -  relative links don't workTesting new DNN Community version - relative links don't work


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