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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...GoDaddy and DNN not in root solution for URLsGoDaddy and DNN not in root solution for URLs
Previous
 
Next
New Post
6/29/2013 12:16 PM
 

Hi,

I've been working with DNN for a couple of years now and just spent some time doing an install on GoDaddy where DNN wasn't in the root.  I'll probably move it into the root later but for now I've found a solution where the users won't see the virtual directory in their address bars.  I figure I'd register to share this since I couldn't find a solution earlier.

Essentially, add a portal alias for the site for both the url with and without the virtual directory.  Then in the ROOT of the hosting account edit the web.config with a couple of rewrite rules.

  1. Rewrite the url to itself
  2. Redirect from the url with the virtual directory to one without
  3. Rewrite the url (if it doesn't have the virtual directory) to one with the virtual directory.

I've outlined the whole process on my blog here

 
New Post
7/17/2013 7:19 PM
 

Jeezy, we are going to try this. We have been trying to figure this out for WEEKS! I can't believe I missed your post before this.

 

 
New Post
8/7/2013 4:56 PM
 
OK, folks... anyone! I tried doing this and am getting a 505 error as soon as I upload the web.config file.

Either I am not using the right syntax (the opening and closing) for the web.config file (it only gives you the rewrite portion of the web.config in the example above).
I'm not putting it in the right place. (I am putting it in the html root of godaddy, not the real root, which godaddy doesn't give access to, or the dotnetnuke installation application root.)

Can anyone give me hints? This is what I came up with that is wrong.




























 
New Post
8/7/2013 4:58 PM
 
OK, folks... anyone! I tried doing this and am getting a 505 error as soon as I upload the web.config file.

Either I am not using the right syntax (the opening and closing) for the web.config file (it only gives you the rewrite portion of the web.config in the example above).
I'm not putting it in the right place. (I am putting it in the html root of godaddy, not the real root, which godaddy doesn't give access to, or the dotnetnuke installation application root.)

Can anyone give me hints? This is what I came up with that is wrong.




























 
New Post
8/7/2013 4:58 PM
 
OK, folks... anyone! I tried doing this and am getting a 505 error as soon as I upload the web.config file.

Either I am not using the right syntax (the opening and closing) for the web.config file (it only gives you the rewrite portion of the web.config in the example above).
I'm not putting it in the right place. (I am putting it in the html root of godaddy, not the real root, which godaddy doesn't give access to, or the dotnetnuke installation application root.)

Can anyone give me hints? This is what I came up with that is wrong.

<!--<configuration> -->
  <!-- The system.webServer section is required for IIS7 compatability It is ignored by IIS6-->
  <!-- <system.webServer>-->
  <!-- <rewrite>-->
     <!-- <rules> -->
<!-- <clear />-->
      <!-- <rule name="Remove Virtual Directory">-->
         <!-- <match url=".*" />-->
         <!-- <action type="Rewrite" url="{R:0}" />-->
       <!-- </rule>-->
       <!-- <rule name="Rewrite DotNetNuke to Root" stopProcessing="true" enabled="true">-->
          <!-- <match url="^web$|^web/(.*)$" />-->
          <!-- <conditions>-->
          <!-- </conditions>-->
          <!-- <action type="Redirect" url="{R:1}" redirectType="Permanent" />-->
       <!-- </rule>-->
       <!-- <rule name="Rewrite Root to DotNetNuke " stopProcessing="true" enabled="true">-->
          <!-- <match url="^(.*)$" />-->
          <!-- <conditions logicalGrouping="MatchAll">-->
 <!-- <add input="{HTTP_HOST}" negate="false" pattern=".+\.thecompanionprogram\.net$" />-->
 <!-- <add input="{PATH_INFO}" negate="true" pattern="^/web$|^/web/(.*)$" />-->
          <!-- </conditions>-->
          <!-- <action type="Rewrite" url="thecompanionprogram/{R:1}" />-->
       <!-- </rule>-->
     <!-- </rules>-->
   <!-- </rewrite>-->
<!-- </configuration>-->
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...GoDaddy and DNN not in root solution for URLsGoDaddy and DNN not in root solution for URLs


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