Hi @aaron13100
What you need to know is that, by default we try to generate usernames from the name that comes from the provider.
If the name contains special characters then we won’t be able to generate a valid username since WordPress doesn’t support special characters in usernames.
Normally in this case, we generate a unique and random username for the user. In your case this doesn’t happen, because you probably used the “Username prefix on register” setting of the given provider.
In such cases this is what Nextend Social Login does:
- we sanitize the given username. Since it contains special characters the sanitized username will be empty.
- we add the specified prefix before the sanitized username, so if your prefix is “Google_” then we will try to register the account with the username “Google_”
- If an account with such username already exists, then we will append a number after the username. E.g. If an account already exists with the username “Google_” then we will try “Google_1” if that already exists as well, then we will increase the number by 1 ( so it will be Google_2 ) and we will check if that username is free or not. We will continue doing this until we find a username that is free and we will register the account with that username.
So don’t worry, this way each account will always have a unique userID, even if we can not generate a username from the given name.
Note:
We also try to store the first name and last name. There you will find the name with the kanji characters, since WordPress allows the special characters there.
