Joomla user not created when & used in names

  • Jeff
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
More
10 years 1 month ago - 10 years 1 month ago #71748 by Jeff
Hi, When creating a new membership, many of my clients sign ups are married couples. Often they put both their names in using the ampersand character "&" [Jack & Jill]. Joomla does not accept this and the Joomla user is not created, there is no warning to the user.
Can this character and other non legal characters be blocked using the validation rules? If so what do I need to add to the validation config for the field?
Last edit: 10 years 1 month ago by Jeff.

Please Log in or Create an account to join the conversation.

More
10 years 1 month ago #71779 by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Joomla user not created when & used in names
Hi Jeff

Is this name or username ? Please give me more information so that we can check it further

Regards,

Tuan

Please Log in or Create an account to join the conversation.

  • Jeff
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
More
10 years 4 weeks ago #71833 by Jeff
We're using the "email as username" plugin which creates the username from the firstname+lastname. So in effect the field that causes us the problem is "first name". People register as a couple using the "&" which Joomla rejects.

The membership is created but not the Joomla member. I was hoping I could find a way to validate the first name by making illegal characters invalid.

Please Log in or Create an account to join the conversation.

More
10 years 4 weeks ago #71859 by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Joomla user not created when & used in names
Hmm, OK. I will try to check the Joomla core API again to see what's causing this and implement the changes to the next version (which I will release this week)

Regards,

Tuan

Please Log in or Create an account to join the conversation.

  • Jeff
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
More
10 years 2 weeks ago #72197 by Jeff
Hi, Were you able to identify the source of this problem for the 2.1 upgrade?

Please Log in or Create an account to join the conversation.