Hi all, New to DNN. Using 5.0. Have created my local site. Have worked through the modifications (SQL, web.config, offline.htm etc) required to upload the site. Host has restored the database successfully (I am able to connect to it and see the tables. After uploading, I got an error to say that it probably wasn't configured as an application. The host modified this through IIS and confirmed I am running ASP.Net 2.0. Now I don't get anything :| I have a redirector page for each domain to a custom folder and the file to load is default.aspx Can someone plz help? TIA, Seano

I'm not sure what you mean by a redirector page and custom folders. It sounds like you have changed the basic structure of DotNetNuke. Can you give a few more details?

I currently host for a few customers at a 3rd party host.

Each customer has a folder in my wwwroot e.g CustA, CustB, CustC. My landing page has a default.asp page that re-directs each domain (CustA.com) to the start page in the CustA folder.

CustC is the customer I have just created a DNN solution for as they want to be able to maintain their own content.

The re-redirector for CustC is: Cust/default.aspx

I am assuming that the landing page for the DNN site is default.aspx?

TIA,
Sean.

Where are these customer-specific directories?  Did you create them manually, or are they directories for portals created in DotNetNuke.

I create the custom folders.

I have 2 folders in the offering from my hosting provider:
database and wwwroot

I create additional folders beneath wwwroot to host each customer's website. The FULL DNN installation (as per the upload instructions from Lee ) is loaded into the customer's folder.

My wwwroot has a default.aspx which has a redirection clause: If there is a request for the custA url, then load the custA landing page in the custA folder beneath wwwroot.

So a request for www.custa.com > wwwroot/custa/index.htm

TIA,
Sean.

I have resolved this.

Basically I was essentially replicating the portal functionality (thanks to your videos Lee!) within DNN, but with a page re-director.

This does beg the question though:
It seems that all requests via DNS are managed by the host and directed to the relevant portal within DNN. What would happen if I have a non DNN site (pure HTML) and I wanted to run that alongside DNN?

Sean.

I'm not sure, usually I would setup each DNN installation as a separate website / application in IIS, so I would do the same for a separate html website. Perhaps it is best to ask your hosting provider as they will be able to provide tips on your current hosting setup.