Difference between revisions of "UNIQUE MEMBER NAMES"
From TMM Wiki
Jump to navigationJump to search (Created page with '== 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…') |
|||
| Line 12: | Line 12: | ||
* unique across sites for joins but site specific for xsells -- this replaces selecting only UNIQUE_USERNAMES | * unique across sites for joins but site specific for xsells -- this replaces selecting only UNIQUE_USERNAMES | ||
<br> The second five options allow for new functionality -- letting usernames be unique across sites, but allowing exceptions if the email is also a match | <br> 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 across sites for xsells and unique unless emails match for joins | + | * unique across sites for xsells and unique unless emails match for joins -- Usernames for xsells must be unique 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. |
* not unique across sites for xsells and unique unless emails match for joins | * not unique across sites for xsells and unique unless emails match for joins | ||
* unique across sites for joins and unique unless emails match for xsells | * unique across sites for joins and unique unless emails match for xsells | ||
* not unique across sites for joins and unique unless emails match for xsells | * not unique across sites for joins and unique unless emails match for xsells | ||
* unique across sites unless emails match for both joins and xsells | * unique across sites unless emails match for both joins and xsells | ||
Revision as of 13:14, 24 December 2009
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.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:
- only unique within site -- this is the default setting.
- unique across sites for joins and xsells -- this replaces selecting both UNIQUE_USERNAMES and XSELL_UNIQUE_USERNAMES
- unique across sites for xsells but site specific for joins -- this replaces selecting only XSELL_UNIQUE_USERNAMES
- unique across sites for joins but site specific for xsells -- 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 across sites for xsells and unique unless emails match for joins -- Usernames for xsells must be unique 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.
- not unique across sites for xsells and unique unless emails match for joins
- unique across sites for joins and unique unless emails match for xsells
- not unique across sites for joins and unique unless emails match for xsells
- unique across sites unless emails match for both joins and xsells
