I am running into the following issue:Our members have a desire for personalized sites directly from our primary domain in the form of \[code\]http://www.example.com/membername\[/code\]. I am looking at possibly solutions in two ways but neither are ideal (will be explained below). Method 1 - \[code\]?Member=\[/code\]In this method, I simply create a custom URL and store the information in the member's database profile. For example: if I want my "custom" URL to be jm4, for a consumer to visit my site, they must type in \[code\]http://www.example.com?Member=jm4\[/code\].The site, of course, does a \[code\]$_GET['Member']\[/code\] to lookup the member information, stores the primary data in Session from the index page, then redirects to a homepage. The consumer no longer sees the membername in the URL but instead sees all the page names for www.example.com as if they simply visited the parent domain to start (each member's page has custom information however).While this method works it presents the following problems:
- The URL is not nearly as easy as \[code\]/jm4\[/code\]and any errors typing out thewildcard \[code\]?Members=\[/code\] will result inpage error. Also, This method keepsthat particular member's informationin session (which is necessarybrowing from page to page on thatparticular member domain) andprevents somebody from simply typing\[code\]http://www.example.com?Member=name2\[/code\] tovisit another site without clearingtheir session or closing the browser.