I created a DNN site where people can sign up to be affiliates.  If they do, they basically get the same site except an extension to the URL. For example, my site is www.mysite.com and they would have www.mysite.com/joe_thomas or www.mysite.com/3543.  So that site looks exactly the same, but I need to be able to track things by their login.  Their sales, etc.Do I need to make a portal for each affiliate?  What is the best bet to do this?

Hey,

That sounds like what I need.  Could you tell me how to setup a child portal?  And is there a way to automate the creation of it.

Here is the basic business model. Joe Thomas has a child portal on the site.  He invites two of his friends to also join the sites and become affiliates.  So he gives them his child portal and they register as well. The key here is I have to link their signup with Joe Thomas' account so he gets credit for getting them to join.  I am not sure that this is built in yet.  If not, I have to figure out how to do that.  Any ideas?  It would be nice to edit the registration form so an extra hidden field is added so that when one registers it keeps track of who their sponsor is.

Thanks for your help

Christian

Can you be more specific?  You can always just assign folks a page and use a url like www.mysite.com/default.aspx?tabid=xxx.  But in order to get the kind of addressing your are looking for ( i.e. without using a file extension ) either IIS must be updated, or there must actually be a physical folder & default file present.  DNN actually creates the folder and a default.aspx file which is hit when you create a child portal.  This is an IIS issue, not a DNN one.

I believe there are some 3rd party solutions out there for this as well... Inventua HREF Exchanger, I think, is one?

btw ~ The multiportal model is what DNN was built for.  Additional tables are not created, just additional ROWS in the tables.

Cheers

Scott Willhite, Co-Founder DNN