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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0URLS, DNN, rewrites and http handlersURLS, DNN, rewrites and http handlers
Previous
 
Next
New Post
2/19/2007 9:43 AM
 

I think someone has mentioned this before but all my serches cant seem to pull up the thread so I was going to ask here and if someone knows the thread please point me to it

I am trying to build a store and one of the things I want to do is have a place where affiliates can easily point people to buy stuff now i know i can do something like

http://domain.com/affliates/tabid/65/affilid/15674/default.aspx

but thats a bit large and unwieldly I wanted to create something a little smaller - I have seen on a few sites where the affliate is given an address like:

http://domain.com/affliatename

Is there anyway in DNN to do this or would I have to have (in my projected case) hundreds of folders with pages redirecting to the tab of the affiliate - it seems to me there should be some possible way of intecepting those requests and doing something with it

This may be a broader asp.net question and not so specific to DNN - one suggestion I have had is to make an extension of my own like affliatename.sell and then tell IIS what to do with that extension

Anybody got good ideas or resources I can look at for this?

TIA


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
New Post
2/19/2007 10:22 AM
 

This definitely possible with DNN. I can think of 2 options. First one is to adjust the siteurls.config to have a custom redirect, but that still requires something like domain.com/default.aspx?affiliateid=1234 (which would need to be redirected to domain.com/affiliates/tabid/65/affiliateid/1234/Default.aspx)

Another option is to write your own http handler or adjust the one DNN uses. What I've done once, is copying the HTTP handler DNN uses, using my own namespaces and inserting some redirections based on specified URL's. Note: you do need to use an URL that mappes to the .NET process (*.aspx, or adjust IIS) and you need to alter your web.config to use the new HTTP handler.

 
New Post
2/19/2007 10:44 AM
 

CasperJuna - Okay what kind of redirections - I havent looked that handler over at all yet but will - can you tell me what you did so I can get an idea if that will work for me

TIA


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
New Post
2/19/2007 10:54 AM
 
I'll get back to you later today about what I did, or where you need to make adjustments. Do you have experience in developing modules, and have you ever run DNN in debug mode? If not, try to set that up first, and add a few breakpoints in the http handler.
 
New Post
2/19/2007 10:57 AM
 

yeah i can do all that just being lazy  and hoping someone else will point me to what I need

TIA


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0URLS, DNN, rewrites and http handlersURLS, DNN, rewrites and http handlers


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