Hello,

Instead of making tests on my live site, I recently seen various tutorials concerning installing DNN locally on my machine.
Everything is working well, but...

If I install a new fresh version on my local machine, in a folder called "mydnn", all my images paths are :
- /mydnn/Portals/0/images/myimage.gif
Instead of the usual
- /Portals/0/images/myimage.gif

If I look into the HOST SETTINGS, I see:
- Relative path /mydnn
On my live website, I have relative path which is empty...

WHY ??? I have also tried to restore my database locally and my zip files, everything is ok, excepted all the images which are broken (due to this relative path). I do not want to modify ALL my HTML/Text Module as well as all Scott News Articles !!! Anybody know how I can modify this ???

DV FX

I think the most important thing here is to use your default website under IIS and redirect it to your DNN install. This will eliminate any strings after "localhost". For example: If you create a new virtual directory "mydnn" under the default website, when working in your dev environment and you call a page in your website, it will return http://localhost/mydnn/Portals/0/images/myimage.gif

But if you use the "default website" and setup http headers and redirect it to your DNN install with the local path, it will eliminate the virtual directory "DNN". Thus you get: http://localhost/Portals/0/images/myimage.gif

I found an in depth tutorial on this I believe on DNN that was very helpful and wished I bookmarked it.

I finally dug back and found the answers to this..............I've been running by dev sites this way for some time.

1. IIS: direct the default website to DNN install folder
2. Go to "properties", "HTTP headers" tab
3. add your headers IE: "mysite: mysite"
4. browse to "C:\WINDOWS\system32\drivers\etc"
5. open "hosts" file in notepad or wordpad
6. update the host names with your machine IP and desired hostname IE: mydomain.com
7. Make sure to restart IIS, and update your aliases in DNN for the desired portal

I've done this with 3 domains and it works GREAT! The only problem with this solution is that it will always direct to your local dev regardless if you have a live site because you are tying the domain name directly to an IP address on your machine. Also if you have multi aliases for one portal, you will have to do multiple logins IE: localhost to mysite.com.

I've been able to browse directly to "localhost" using this method and also to "mysite.com" this way as well and being in my dev environment, I just have to remember if I hardcode any links to make sure I include the domain name.

Hope this helps Declic, I knew I'd stumble on it again sooner or later. I'm still looking for the tutorial on this to share with everyone else. (wish i bookmarked it)