Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Solution: GoDaddy DNN on root, no subdir in URL, multiple domains hostedSolution: GoDaddy DNN on root, no subdir in URL, multiple domains hosted
Previous
 
Next
New Post
3/13/2008 3:36 AM
 

After reading a million posts, I found a post somewhere (I think on this site, but not sure) which gave very clear instructions on how to move the DNN install to the root of your deluxe hosted site. I copied the steps and it worked perfect! Yes, you can eliminate the subdirectory, look like a real web site, and set up any other domains that you host as portals, also without any subdirectory in the URL. It's not hard, folks, and I'm staying up late to share because i'm happy to give a little something back if it can help others. Once you move the site, you can point all your domains to your root, and just indicate your domains in the portal's HTTP alias. No need to re-install & no more redirects. A million thanks to whoever posted the basic steps. I'm adding some detail that I hope is helpful for the benefit of ALL THE POSTS complaining about this, because this fix really works. GoDaddy doesn't support install at the root by default, but moving it after the fact is not hard. Here are the steps. 

1) Check that the Root and DNN directories have the same permissions. You might need to adjust through IIS Settings or File Manager(I didn't). Check the bottom of this page for good advice on security: http://www.northernstarsolutions.com//tabid/61/Default.aspx.

2) Backup both your DNN web installation and your database (in database section, click the pencil to edit, then the Backup icon at the top)

3)  Create an html file called app_offline.htm into the DNN directory, taking the site offline.

4) Update your site's existing portal alias record in the database (the HTTPAlias column of the dnn_PortalAlias table) from (example) mysite.com/dnn to simply mysite.com. This is the only slightly advanced step. From the GD control panel, go to databases/SQL Server/Open Manager. Enter your DB username & pass (user is like tri + 12 #s). Once you connect, go to Query Analyzer, and execute this(omitting quotes) "select * from dnn_PortalAlias" This shows you all your aliases for any portals you have. So, if your main site has portal ID of 0, and your current alias is mydomain.com/dnn, you would update it to mydomain.com by executing this:

UPDATE dnn_PortalAlias
  SET HTTPAlias = mydomain.com
  WHERE PortalAliasID = '0'

5) Now move the contents of the current DNN folder into the root. Easiest way is to FTP it back home, then up into the root. It takes a little while, but just sit back and think how happy you are gonna be soon. Google's gonna see you as a real site!!  :-)

6) Update any references you might have in your web.config file to your old site path.

7) Remove the app_offline.htm file and point a browser at the default.aspx file.

8) Have fun with a real DNN install on GoDaddy!!

 
New Post
3/13/2008 9:41 AM
 

This is great to note that you can do it all properly.

However, I would caution that if you have to go though this much hassle that it might be worth spending an extra few dollars a month to avoid the hassle and potential issue.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
3/13/2008 10:57 AM
 

well, that article is quite old and godaddy made it easier to install app at root level.

I'm currently publishing advanced installation tutorials for dotnetnuke users that use godaddy for hosting.

if you are interested checkout my blog > http://www.mynetnuke.com/Blog.aspx


Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey
 
New Post
3/18/2008 11:59 AM
 

Hi, I have done exactly what you shown here.  Everything worked except that I could not use any of the Admin items.  Here is the error message:

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The code subdirectory '/Admin/App_Code/HTML/' does not exist.

Source Error:

[No relevant source lines]

Source File: d:\hosting\huanzhong\web.config    Line: 111

Anyideas how to fix this? Seems like it is looking at the wrong App_code directory.

 
New Post
3/31/2008 11:56 PM
 

I had that error once before - - it was the permissions

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Solution: GoDaddy DNN on root, no subdir in URL, multiple domains hostedSolution: GoDaddy DNN on root, no subdir in URL, multiple domains hosted


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out