iFinity

We have already downloaded your trial version and have been testing that on our demo site & have been able to successfully reconfigure our static links / tabs for eg :from : http://bizkatalyst.com/healthcaresolutions/FINDHEALTHCAREPROVIDERS/Doctor/tabid/64/Default.aspx to
http://bizkatalyst.com/healthcaresolutions/doctor.aspx
 
However what we need to know is whether your product can help us reconfigure the links for our dynamically generated pages (i.e the pages which are thrown up as a result of a search query run on our database...
 
For eg if after reaching our doctor tab, someone searches for a cardiologist and hundreds of names are thrown up in a certain city. Now when he clicks on any one name, the complete details of that doctor are thrown up on a separate page...generated through a query string.
 
For example :  http://bizkatalyst.com/healthcaresolutions/doctor/ctl/viewdoctorforregistered/mid/412.aspx?doc_id=del01%5Cdoc-78
 
We essentially want to replace this with something like
http://bizkatalyst.com/healthcaresolutions/doctor/1589764
 
So that all these pages are also indexed by the google crawlers (as we are told that the crawlers are not able to crawl links with ? and % signs in them).  This is critical for us as we want that people searching for an X doctor in ask4healthcare on google should be directly able to reach the profile page like http://bizkatalyst.com/healthcaresolutions/doctor/1589764
 
This is how it is done at portals like healthgrades for eg if you search for (Doctor Smith Healthgrades) on google, the link to his profile page shows up in google search results directly :http://www.healthgrades.com/directory_search/physician/profiles/dr-md-reports/dr-jeffrey-smith-md-45bb3b1b
 
Hope I have been able to explain this.
 
Shall wait for your revert.

The simple answer is that the module cannot improve the Urls beyond the example that you gave : http://bizkatalyst.com/healthcaresolutions/doctor/ctl/viewdoctorforregistered/mid/412.aspx?doc_id=del01%5Cdoc-78
 

I assume this Url was generated with the Url Master moduel installed.

If you would like to have Urls like this one:

http://bizkatalyst.com/healthcaresolutions/doctor/1589764
You would have to redo your module code.

Specifically :  change the url for /ctl/viewdoctorforregistered from a specified control to either having the viewdoctorforregistered as the default control for the module, or create a separate module with this control as the default, if that isn't possible.  This will remove the /ctl/viedoctorforregistered and the /mid/412 out of the url.

Doing this action is just a change in the DNN module configuration, and would leave you with

/healthcaresolutions/doctor?doc_id=del01%5cdoc-78

Next, change your doctor id value so that it doesn't include encoded Url characters.  The reason the Url looks like this is because of the url-encoded value in the 'doc_id' value.  If you decode this value, you get del01\doc-78 .  You need to change this value so it doesn't include a backslash ( you could replace it with a hyphen) , and you'll get a Url like this:

/healthcaresolutions/doctor/doc_id/del01-doc--78

The reason it is being appended on the end is because the regex value that filters out items for the friendly url path detects the url-illegal backslash, and doesn't include it in the friendly url path.

Finally, if you want to remove the doc_id value then you cna change your module to look for the qureystring items based on position, rather than key.  Specifically, instead of looking for Request["doc_id"] you can look for the first item in the request.querystring keys collection, and use this as your value.  This would give you a value of

/healthcaresolutions/doctor/del01-doc-78

Note that none of these changes involve the module at all - they are all aimed at changing the way your DNN module is generating Urls to better formulate friendly urls.

If you were to re-write the application to do this, you might as well start including the doctor name in the Url (if that's important) so you get

/healthcaresolutions/doctor/del01-doc-78/dr-smith

Please note that the advice you have been given about search engines not being able to index urls with ? and encoded characters is outdated advice.  You can do a search for somethign commong like ?threadid= or even ?tabid= and you will see millions of indexed Urls.  Search engines can all crawl Urls with querystrings. 

With regards to the first question, the default control for a module is the one marked as 'view' in the module type.

This blog entry covers this : http://www.ifinity.com.au/Blog/EntryId/48/Designing-Structuring-and-Architecting-DotNetNuke-reg-Modules

With regards to the second question ; you can experiment by requesting any page with the Url that you want.  Then, in your vs debugger, inspect the Request.QueryString object.  If you iterate through the keys, you will find that every odd numbered parameter in the list will be a key, and every even numbered will be a value.

So /first/second/third/fourth as a url will look like this in the querystring items collection:

item 0 key = first

item 0 value = second

item 1 key = third

item 1 value = fourth

So, instead of looking for a specific querystring value based on the known key, use the position to find things instead.  You'll have to handle cases where the order has been messed up and show errors or redirects, but you shoudl be able to figure it out.