|
 |
 |
 |
Jul
2
Written by:
Travis Whidden
7/2/2007 4:29 PM
As some of you may know, I recently released a module for DNN that you can use to help redirect your clients to the correct url. This is very handy if you are moving a website to DNN, and dont want to loose your search engine postion links.
I recently updated my code to support tracking hits to yoru pages that result in 404, file not found codes. It increments each time they are entered.
Here is an example of one of my websites I run that used to be written all in asp. (click ot enlarge)

As you can see, this is very good information to have so you dont loose valuable clients coming to your website.
This product can be purchased on SnowCovered for $10 bucks as of today:
http://www.snowcovered.com/Snowcovered2/Default.aspx?tabid=242&PackageID=7640&r=7955725ffc
Tags:
7 comment(s) so far...
Re: Update for DNN module Smart Redirect for 404 errors. New undefined url tracking
Looks like a promising module. My only concern is that it does not return a 301 status code when redirecting the the new URL, does it?
By Tom Kraak on
7/4/2007 11:54 AM
|
Re: Update for DNN module Smart Redirect for 404 errors. New undefined url tracking
Actually, it does do a 301 now as of the last module I submitted to Snowcovered. I should have pointed that out.
By Travis Whidden on
7/4/2007 12:16 PM
|
Re: Update for DNN module Smart Redirect for 404 errors. New undefined url tracking
Excellent! Thanks Travis.
By Tom Kraak on
7/5/2007 10:41 AM
|
Redirection to dynamically created pages using HJT Redirector
Hi,
We had purchased the HJT Redirector module sometime back and it has been working fine for all the old URLs (on our sites) that needed redirection. However, we have made some changes to the design of our sites - from being English only sites, we have brought in the concept of multi-lingual sites as well as the concept of geosites. Our site has been built using DotNetNuke version 4.5.5 and uses the HJT Redirector module version 1.01.00. The URLs for the pages are created dynamically based on which ever language has been selected for the site, ie the querystring is generated on the fly whenever the user clicks on the language of his preference, from the site. We have configured our sites in such a way that our main website is say "http://www.example.com" and all other country specific sites are virtual directories under this website, for eg - our German site would look like "http://www.example.com/DE" where "DE" signifies the German site which is a virtual directory under " www.example.com". Continuing with our example, this German site has two languages namely "English" and "Deutsche", so the URLs that get created on the fly are "http://www.example.com/DE/Home/tabid/36/L/en-US/Default.aspx" and "http://www.example.com/DE/Home/tabid/36/L/de-DE/Default.aspx", where "L/en-US" and "L/de-DE" signify the "English(en-US)" and "Deutsche(de-DE)" languages and "Home/tabid/36" signifies the home page of the site. It so happens that some of the pages are also created on the fly based on the content of the page. We have written code to dynamically append the "L/locale" (example "L/en-US" or "L/de-DE") to any URL that the user has requested for (for example, for the first time the user is taken to the Home page, by default the English language content is shown and hence the URL constructed dynamically will have "L/en-US" in it). Now, we have noticed that whenever we give new URLs in the settings of the HJT Redirector module (without the "L/locale" information) in it, on browsing to the old URL, it throws the "Page Not found" page. We then edited the new URL and put in the "L/locale" information but it didnt work even then. After looking into your code using the reflector tool, we saw that you are using the property "Response.RedirectLocation" (in the page_load section) rather than "Response.Redirect". As in DNN, we are mostly making use of "Response.Redirect", do you think this has anything to do with the issue that we have at hand? Please do let us know your views on this. Any help from your side will be appreciated.
By Deepa Menon on
12/23/2008 5:59 AM
|
Re: Update for DNN module Smart Redirect for 404 errors. New undefined url tracking
Deepa,
I replied via email to assit you with your issue. Thanks.
By Travis on
12/23/2008 9:41 AM
|
How to upgrade module
Our site uses HJT redirector version 00.00.05 (as listed on the module definitions page) How do I upgrade to the latest version?
By Joshua Fisher on
1/7/2009 12:22 PM
|
Re: Update for DNN module Smart Redirect for 404 errors. New undefined url tracking
thanks
By sudarshan on
3/10/2010 3:48 AM
|
|
|
 |
 |
 |
 |
|
|
|
|