DNN 3.2.2

on our dev site, I installed the way DNN said to, with a virtual DotNetNuke folder. Now we are stuck with that in every path.

I want to move the DNN files up to the root and get rid of that folder; I am not finding much help for doing this on the DNN sites.

I have set up a new test DNN site on a virtual IIS service to try to figure this out.

Our setup:
*.wbtdev.net points to one IP on the Server: ...50.
That server has a default IIS site with no host header defined so it will catch all requests
dnn.wbtdev.net points to the same IP, and there is a second IIS server instance with host header of dnn.wbtdev.net

on this second server, I installed DNN on the root, to a new SQL db just for this test.
this runs fine.
the alias list on the default portal is:
Edit   dnn.wbtdev.net/dotnetnew/
 dnn.wbtdev.net
Edit  dnn.wbtdev.net/test2/

Now I want to move the DNN files to a new folder: /test2/
 have the ASP.NET machine account set to full permissions on the root and all folders of this site.
  I stop and restart this virtual server; I clear the cache of my browser (actually shut down the browser and start it up again, but then clear cache and cookies). (cookies because I just found a post that suggested that)
 then sent the browser to dnn.wbtdev.net/test2/
  and I get a yellow screen with this error:
Server Error in '/' Application
 I tried changing the <customErrors mode="Off"/> tag in web.config as that page suggests for getting error messages but it never makes any difference.

I drag the files back to the root, stop/start the IIS server, clear the brower, reload and all is well on the original site again.

any thoughts on where I might find what is locking the site to the original folder (root)?

Would I be able to edit that to get it all to work?

thanks for looking at this with me.

tomvw

Well, I never got an answer here but Nina Meyers of www.xd.com.au helped me out.

I added an alias to each portal on the dev server so that they would be found by the new DNN service minus the /DotNetNuke/ folder.

Then I stopped the IIS service,
made the DNN folder the root of the IIS web service,
removed the virtual /DotNetNuke/ folder that was pointing to this same DNN folder,
and turned the IIS server back on.

And everything came up fine.

The only fixes were that any text modules that had image links in the text had to have the /DotNetNuke/ folder removed from their image path.

I still don't see why just dragging the DNN files up to the root didn't work, but this does work.
tomvw

Thanks for posting the info here,

Lee

How to fix image links for all content? Does anybody have an idea?

What do you need to fix with regard to links?

If the links are in HTML modules, you may be able to use Engage Software's F5 module. It's free, and it can be used to go search/replace on all of the HTML modules in your site.