Hello!

We have been developing our site in DNN for the past few weeks and it is now time for it to go live. The dev environment was http://domain.com/DotNetNuke but the site is now supposed to run from a virtual directory in localhost. I've set up such a directory called portal and, since I am unfortunately no expert on IIS, use a default.aspx in the localhost root to redirect to that virtual directory.

Now, all image links are broken and the "Browser server" function available from the Edit HTML module area shows nothing, this since all links point to /Portals/0, and are relative from the root of localhost, not localhost/portal! If I check host settings, my relative path is /portal, which is correct. Why aren't all my image paths resolved from localhost/portal then?

I have found threads discussing this kind of problem, but it is usually the other way around, with an extra folder in the image path. The solution then has been to simply create that folder, but understandably, I can't do that.

Any help is highly appreciated, I am getting balder and balder...

Hi Ian, thanks for your reply!

Though, the thread you linked to addresses the exact same problem I talked about in my original post, the problem of moving DNN from "root" to a subfolder of root. I want to go the other way round and get DNN to work in a subfolder of localhost root. Is my only option then to change all image paths to portal/Portals/0... ? I could do that, but how will I get the image upload to work? By that, I mean the editing of a HTML/Text module and the rich text box which allows browsing for certain images on the remote server. This function gives me a blank window, and even if I change all image paths to the corrects ones, this function will still not work without me changing some base path for it I guess...

Any further thoughts? Am I better off with a clean install/import?