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 ...DNN in a sub on Godaddy with Google Sitemap DNN in a sub on Godaddy with Google Sitemap
Previous
 
Next
New Post
9/4/2006 10:58 PM
 
I use a piece of software called SoftPLUS GSiteCrawler. You can do a google search for it. It is free and works really well. It crawls your site, generates a sitemap, and uploads it via FTP to your site.
 
New Post
9/4/2006 11:01 PM
 

I havent had a chance to search for your thread, but here is the code that I use:

<%@ Language=VBScript %>
<%
response.status="301 moved permanently"
Response.AddHeader "Location", "http://www.vegasvic.biz/vegasvic/"
%>

I just made an index.asp file and put it in the root of my site. Google sees this as a 301 permanent redirect. It literally took google a month of settling down before it started reading my sitemap properly and reported that it could index my home page. I kept getting the error that my home page is inaccessible.

Hope this helps . . . let me know more specifics and maybe I can assist.

Vic

 
New Post
9/12/2006 8:23 PM
 
I've seen several posts along the lines of "How do I install DNN into the root for an account at Godaddy" or other cheapo hosting provider.

I recently ran across an ASP.NET suggestion on redirection - to use Server.Transfer instead of Response.Redirect.  Quoting from http://www.developer.com/net/asp/article.php/3299641

Server.Transfer is similar (to Response.Redirect) in that it sends the user to another page with a statement such as Server.Transfer("WebForm2.aspx"). However, the statement has a number of distinct advantages and disadvantages.

Firstly, transferring to another page using Server.Transfer conserves server resources. Instead of telling the browser to redirect, it simply changes the "focus" on the Web server and transfers the request. This means you don't get quite as many HTTP requests coming through, which therefore eases the pressure on your Web server and makes your applications run faster.

Secondly, Server.Transfer maintains the original URL in the browser. This can really help streamline data entry techniques, although it may make for confusion when debugging.

That's not all: The Server.Transfer method also has a second parameter—"preserveForm". If you set this to True, using a statement such as Server.Transfer("WebForm2.aspx", True), the existing query string and any form variables will still be available to the page you are transferring to.

Since any installation of DNN will have access to the ASP.NET functions, is this not an easy way to accomplish the pseduo-installation of DNN into the root of a webiste - or at least make it seem to the outside world that such is the case?

If you have experience with this - or have tried it and would like to share your server.transfer code for noobs, please respond.


Thanks!
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN in a sub on Godaddy with Google Sitemap DNN in a sub on Godaddy with Google Sitemap


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