Difference between revisions of "UNIQUE MEMBER NAMES"

From TMM Wiki
Jump to navigationJump to search
 
Line 6: Line 6:
 
* XSELL_UNIQUE_USERNAMES Requires cross sale usernames to be unique across all sites. If there is a match, the new xsell username is automatically renamed.
 
* XSELL_UNIQUE_USERNAMES Requires cross sale usernames to be unique across all sites. If there is a match, the new xsell username is automatically renamed.
  
On NATS version 4.0.69 and greater, these variables have been replaced with a new variable --UNIQUE_MEMBER_NAMES-- with 9 options . The first four of these options replicate existing functionality from older versions:<br>
+
On NATS version 4.0.72 and greater, these variables have been replaced with a new variable --UNIQUE_MEMBER_NAMES-- with 9 options . The first four of these options replicate existing functionality from older versions:<br>
  
 
* only unique within site -- this is the default setting.
 
* only unique within site -- this is the default setting.

Latest revision as of 11:21, 10 May 2010

UNIQUE MEMBER USERNAMES

By default, usernames are unique only within an individual site. Prior to NATS version 4.0.69.1, there were two configuration settings that could affect username uniqueness.

  • UNIQUE_USERNAMES Require usernames on the join form to be unique across all sites. If there is a match, the user must pick a new username.
  • XSELL_UNIQUE_USERNAMES Requires cross sale usernames to be unique across all sites. If there is a match, the new xsell username is automatically renamed.

On NATS version 4.0.72 and greater, these variables have been replaced with a new variable --UNIQUE_MEMBER_NAMES-- with 9 options . The first four of these options replicate existing functionality from older versions:

  • only unique within site -- this is the default setting.
  • unique for joins and xsells -- this replaces selecting both UNIQUE_USERNAMES and XSELL_UNIQUE_USERNAMES
  • unique for xsells -- this replaces selecting only XSELL_UNIQUE_USERNAMES
  • unique for joins -- this replaces selecting only UNIQUE_USERNAMES


The second five options allow for new functionality -- letting usernames be unique across sites, but allowing exceptions if the email is also a match

  • unique for xsells and unique for joins(unless emails match) -- Usernames for xsells must be unique across sites as with XSELL_UNIQUE_USERNAMES. Usernames on the join form must be unique as with UNIQUE_USERNAMES, but allowing an exception if both the username and email match the existing member.
  • unique for joins (unless emails match) -- Usernames for xsells do not need to be unique across all sites. Usernames on the join form must be unique as with UNIQUE_USERNAMES, but allowing an exception if both the username and email match the existing member.
  • unique for xsells(unless emails match) and unique for joins -- Usernames for xsells must be unique across sites as with XSELL_UNIQUE_USERNAMES, but allowing an exception if both the username and email match the existing member. Usernames on the join form must be unique as with UNIQUE_USERNAMES.
  • unique for xsells(unless emails match) -- Usernames for xsells must be unique across sites as with XSELL_UNIQUE_USERNAMES, but allowing an exception if both the username and email match the existing member.
  • unique for xsells(unless emails match) and unique for joins(unless emails match) -- Usernames for xsells must be unique across sites as with XSELL_UNIQUE_USERNAMES, but allowing an exception if both the username and email match the existing member. Usernames on the join form must be unique as with UNIQUE_USERNAMES, but allowing an exception if both the username and email match the existing member.