Last post Jan 23, 2006 03:48 PM by mannyd
Dec 31, 2005 12:36 PM|Sedona|LINK
How do I get my website to go live? The website was built using the NotNetNuke platform and is hosted with godaddy. I need to be able to access the website as
www.domainname.com and not as it is now in development stage:
www.domainname.com/domainname What are the steps, the code, the options to make this happen?
Please help. I am a newbie .
Dec 31, 2005 03:08 PMfirstname.lastname@example.org|LINK
You either needed to install DNN to the web root so it would be located there, or you need to create a redirect file as your default document in the root so it redirects to the proper location. If you have access to the IIS settings you can simply change
where the home directory points to and point it to your DNN folder to accomplish this.
Dec 31, 2005 03:58 PM|adelinoaraujo|LINK
Jeff, now that you say "redirects" you remind me that DNN 4 is quite slow at start, about 10 seconds, so would you agree that is better to put a simples .asp page with some kind of info and then redirect to the default.aspx?
ya... to avoid users to run away of course... in the live dnn.
Jan 01, 2006 10:30 AMemail@example.com|LINK
I have a number of these set up with an ASP page doing a Response.Redirect. Works fine.
DNN won't be "quite slow" if you have traffic. The pages get cached at the server and resond very quickly until there's a period of time since the last request and the cache clears.
Jan 01, 2006 11:19 AM|Sedona|LINK
Thanks Jeff. Sounds like you are an expert. Well, I evidently did not "install DNN to the web root". Godaddy was promoting DNN 6 months ago and I decided to give DNN a try. Godaddy's navigation just sent me to DNN to start building.
So I guess that means I have to "create a redirect file as my default document in the root". I have no idea how to do that. What is the default document in the root? What would the "proper location" be?
Sorry for being so new.
In the "host" area of my DNN website, I have found the .NetFrameWork number ("The .NET Framework version which the application is running on - specified through IIS") Is this number of use, and if so, what do I do with it? How would I "change where the home
directory point to"? Where would I find the DNN Folder address?
As you can see I am lost? Thanks in advance for your help.
Jan 01, 2006 04:48 PMfirstname.lastname@example.org|LINK
If you're using a host, you most likely won't be allowed to change the location of the web site root. Best bet is to use a redirect file in the root. You should have a web site folder with a DNN folder inside it. In the web site folder you can place a
file with a redirect command, HTML and ASP both are simple to use for this. You will need to check with your host as to how you change the default document or what the default document is. You can leave it as it is and name the redirect file with the same
For example, this file, saved as default.asp (if that's the default ASP document name), would do a redirect to a folder named DNN in the sample.com domain:
<% Response.Redirect(http://www.sample.com/dnn/) %>
Jan 02, 2006 09:31 AM|Sedona|LINK
Thanks Jeff for the detailed directions. I did talk with godaddy and graciously they directed me to the ftp client area and said that my defualt folder was "Welcome.html". Then they told me to google "html redirect" to get the code to use for the redirect.
1. How does the code: <% Response.Redirect(http://www.sample.com/dnn/) %>
differ from this code that I took off a website that I googled.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<title>Your Page Title</title>
<meta http-equiv="REFRESH" content="0;url=http://www.the-domain-you-want-to-redirect-to.com"></HEAD>
Optional page text here.
<meta http-equiv="REFRESH" content="0;url=http://www.the-domain-you-want-to-redirect-to.com"> is the part that actually does the redirecting.
The number preceding the url (in this case zero) tells the browser the number of seconds to wait before redirecting to the new url.
You could set this to 5 and add some optional text to your page - something like:
"Please wait while we redirect you to our new site".
That's it! Just copy the code, save it (i.e. save as index.html) and your html redirect will work perfectly.
2. Going with your code: I assume that I place the redirect code in the newly created file. Yes?
3. Should I save and name the file "welcome.html" as you suggest or would I name it "index.html" as stated above -- or does it matter?
4. Using your code what would the URL be in the redirect code? Is it
http://www.myDomainName.com/welcome.html? If so, will this activate the domain - so that when I enter into a browser:
www.myDomainName.com it will be found and displayed as such in the browser. Or will it be found and redirect to
www.myDomainName.com/myDomainName which is the development URL and therefore be shown in the browser?
Thanks for your expertise and patience.
Jan 02, 2006 10:14 PMemail@example.com|LINK
It uses the HTTP Meta REFRESH tag, where mine was an ASP redirect. End effect is the same. In fact, in your case I'd go with GoDaddy's recommendationa dn use a welcome.html file with the redirect code above. You need the welcome.html file to be:
<meta http-equiv="REFRESH" content="0;url=http://www.MyDomainName.com/myDomainName/default.aspx">
In other words, the redirect is to the exact path and file name to get you to your website file.
Jan 02, 2006 10:33 PM|jeffkw|LINK
Jan 03, 2006 10:01 PM|Sedona|LINK
Thanks for your help, Jeff. I succeeded in creating a redirect file and...
When I type in the domain name: www.MyDomainName.com it redirects to
www.MyDomainName.com/MyDomainName, which is displayed in the browser. I am dissapointed that the browser displays the extra "/MyDomainName" at the end. I guess there is nothing I can do about that. Not
sure if I will ever use DotNetNuke again. Although your guidance and this forum has been great.
Thanks again. Happy New Year.
Jan 04, 2006 12:02 AMfirstname.lastname@example.org|LINK
It's not DotNetNuke. It's that you installed DNN to a subfolder of the web site. If you saved a file to c:\temp\myfile.txt, you can't access it at c:\mytext.txt.
You need to install DNN at the root of your web site if you want it to display the URL as you wish. Which may mean you need to choose a web host with the capability to allow that.
By the way, any ASP.NET application you install to a subfolder or virtual directory will need to be accessed like this.
Jan 04, 2006 07:07 AM|Sedona|LINK
If I recall the installation was an easy process, just went into godaddy and clicked install. The development phase went along okay for a while, then there was a "Server Error". I called godaddy and they "fixed" it. Little did I know.
Thanks again. Next time I will know a bit more before I start a project with godaddy.
Jan 04, 2006 09:01 PMemail@example.com|LINK
GoDaddy may not support installing DNN in the root. Other hosts do.
Jan 23, 2006 03:48 PM|mannyd|LINK