Please Log in to join the conversation.
No, CB attempts to place some kind of username and the fallback is Name fields. Username field is required by the CMS.Is there a workaround to solve this problem ?
No, not out of the box. You could develop a CB plugin that utilizes the trigger onBeforeUserRegistration to apply a new username before the registration occurs. For further information on trigger usage please see tutorials within my signature.I don't need username at all and hided them but could CB create random username to avoid this problem ?
Please Log in to join the conversation.
Please Log in to join the conversation.
Because the username is required by the CMS. CB adds the feature to login via email. You can not simply remove usernames from the picture, they're still required. You could name it something more clever perhaps such as Nickname, which is more common to users or Screen Name.why should I ask my user to set a username if I let them use just their e-mail ?
Please Log in to join the conversation.
Please Log in to join the conversation.
That'd be fine, email and/or user_id are acceptable substitutes as they are both unique.Krileon would it be a bad idea to use CB Subs and through CB Fields integration set each plan to copy the email inside username field ?
Correct, is actually a good idea as long as a user is required to have a subscription upon registration otherwise it'd attempt to use Name.In this way I would still have a username, it would be unique for everybody and it would be easy to remember for users too because it is the same email they use to log in.
Please Log in to join the conversation.