Quick Nav:  Online Store   |   Login | Register

URL Rewrite Question

Rate this topic:

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.
AuthorMessages
maruma
<20 Posts
Posts:9


07/26/2007 11:32 AM  

I just downloaded PageBlaster the other day (free version) and if I get everything working correctly, I will purchase the full version, because I have read great reviews about this module.

I do need help with 1 setting though.

Concerning URL rewriting and SEO:

I have read the following post.

 

http://www.snapsis.com/DotNetNuke/Support/tabid/560/forumid/12/postid/5000/view/topic/DNN-Tips-And-Tricks-5000.aspx

and this one

www.snapsis.com/DotNetNuke/Support/tabid/560/view/topic/forumid/16/postid/6348/Default.aspx

 

 I was able to configure the siteurls.config file in order to allow people to simply enter a url for my site's pages, such as
www.domainname.com/pagename.aspx

My question is the following. Whenever people click a link to the above page from my menu, dnn automatically redirects it but displays the page name with all the standard url:  http://domainname.com/PageName/tabid/51/Default.aspx

This is not the behavior that I am looking for, I want to make every single page appear with the format   www.domainname.com/pagename.aspx, regardless of where it comes from.

I believe that the second post above explains how to accomplish this by adding a rule to the Snapsis.PageBlaster.config file. Is this what I should be adding? Could you please give me an example of a rule which would allow this behavior? I am a little rusty on regular expressions, and the example from the above post talks about the terms page which is more complicated than I need.

Thank you.

 

 

John Mitchell
Posts:3492


07/26/2007 11:50 AM  

If you want to do it globally by just "re-arranging" the Friendly Url that DotNetNuke puts out, you could use this rule:

SearchFor:       (http[s]?://[^/]+)(/[^"]+)(/(?=tabid)[^"]+)/Default\.aspx(?!\?)

ReplaceWith:    $1$3$2.aspx

You will still have the tabid in the Url with that method though.

If you want to make specific page names regardles of what it is named in DotNetNuke then you need a combination of the SiteUrls.config (to map a regular name to a tabid) and an output replacement for each page (like in the terms/privacy post).

The PageBlaster DNN module (paid version) does the virtual path mapping on each page which is more or less what you could do yourself with the SiteUrls.config.

 

maruma
<20 Posts
Posts:9


07/26/2007 12:00 PM  

Thank you John for the quick reply.

Quoting you from your reply, this is what I am interested in doing.

If you want to make specific page names regardles of what it is named in DotNetNuke then you need a combination of the SiteUrls.config (to map a regular name to a tabid) and an output replacement for each page (like in the terms/privacy post).

The PageBlaster DNN module (paid version) does the virtual path mapping on each page which is more or less what you could do yourself with the SiteUrls.config.

 

But, I still have a question, do you mean that there are 2 options in order to accomplish this? I can either do it myself manually, with the 2 config files, or if I purchase the paid version,  there is an easier way of configuring it per page?

 

Thanks

 

John Mitchell
Posts:3492


07/26/2007 12:19 PM  
Yes, it is slightly easier with the paid version.

You still have to configure it in two steps to get a true "url rewrite" though. One step to specify the virtual path for the incoming request, and one step for replacing output text in your html so that you do not have different Urls pointing to the same content. This second step is optional. You also have to place a PageBlaster module on each page that you want to specify a virtual path unless you decide to update the pageblaster mapping table directly which is another XML config file.

If you are wondering why I don't just say "Yes, get the paid version". It is because I didn't really create the module as a Url rewriter. I just added the virtual path mapping to cached pages because it was fairly easy, and added some value since you can specify your own virtual page names if you wanted to. Most people just want a global rule so that they don't have to specify what the url is for each page. In other words, I wouldn't want you to pay for the module as a Url Rewriter unless you really want the ability to manually specify your own virtual paths for each page.
maruma
<20 Posts
Posts:9


07/26/2007 2:51 PM  
Sorry for my delayed response John.
Yes, I would like the ability to manually specify my own virtual paths with the paid version. Does this sound correct:

I am looking to completely eliminate all tabid's from any URL that ever gets presented to the user. I would like my site to function like any other non DNN site would function (concerning the way URL's are displayed). I already have a site built on ASP.NET which I am porting over to DNN, but the only thing I am not liking about DNN is the manner in which URL's are displayed. Furthermore, my goal is to be able to point my internal links to a /pagename.aspx format, and not use DNN's tabid format. Is all of this possible?

Thank you.
John Mitchell
Posts:3492


07/26/2007 3:00 PM  

Yes, that is all possible. 

 

maruma
<20 Posts
Posts:9


07/26/2007 3:03 PM  

Perfect, thank you again.

 

maruma
<20 Posts
Posts:9


07/26/2007 4:00 PM  

Another question John

Once I set all of my virtual url's , do you know if google will index the friendly URL's that I set , instead of the tabid ones?

Thanks

 

John Mitchell
Posts:3492


07/26/2007 4:08 PM  
Yes, the new ones will index as googlebot finds them. If you wanted to remove the old ones from their index then the easiest way would be to block the bot to any Url with /tabid/ in it. Creating a virtual path will not keep the normal tabid urls from working.
maruma
<20 Posts
Posts:9


07/26/2007 4:10 PM  

Oh, I see. I didn't know that. Great info!

I will upgrade to the full module later tonight. Thanks again John.

 

John Terpening
<100 Posts
Posts:80


09/16/2007 9:42 PM  
Posted By John Mitchell on 07/26/2007 4:08 PM
Yes, the new ones will index as googlebot finds them. If you wanted to remove the old ones from their index then the easiest way would be to block the bot to any Url with /tabid/ in it. Creating a virtual path will not keep the normal tabid urls from working.



I have been reluctant to change all of the side-wide URLS, given that I have been getting some backward links pointing to my portal and hate to start all over (or be left with a bunch of indexed broken links). Based on your post, it sounds like the old /tabid/68/Default.aspx style of links still work and the new, rewritten URLS are merely virtual paths to the /tabid/68/Default.aspx style pages? So both /tabid/68/Default.aspx and /home.aspx forms of the URL would work? Does this raise duplicate content issues?

... have 30+ windows and the PB documentation open for my 2 hour commute tomorrow morning, so I apologize if this is a stupid question that is answered elsewhere. ;)

John Mitchell
Posts:3492


09/17/2007 9:56 AM  
Yes, your old links will still work. It may lead to duplicate content, but that is less of a concern and can be phased out slowly.
Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.
Forums >Snapsis Product Support >PageBlaster > URL Rewrite Question



ActiveForums 3.7
Powered by: Snapsis Software