Usernames with special characters causes issues

Bug
1

A user registered with the username “User.Name01” and was subsequently unable to locate their account via the search function. The user then modified their username to “User,Name01,” which also resulted in the same issue of being unsearchable.

In contrast, I tested the search functionality with my personal account “PersonalAccount” and was able to locate it without any issues, both before and after the username change.

The user then changed their username again to “UserName01,” omitting any special characters. This modification appeared to resolve the search issue. However, during our testing process, we encountered an anomaly where the options for “find by username” and “find by email” became deselected. Even though these options were initially checked, the user had to uncheck them, save the changes, and then recheck them to re-enable the options. Notably, other team members were able to create accounts without this requirement.

While this is not a critical issue, I wanted to bring it to your attention as it did introduce some challenges during the setup process.

Thank you for your ongoing excellent work!

2

What did you search? You’ll only be able to search for their name or email when they enabled this in the settings.

Usernames with commas are not really supported (I’ve just pushed a fix to prevent accounts with this username from being registered in the first place).

1 Like
3

It appears that this issue was isolated to a single user. It seems that the problem may have arisen when they switched from using a period to a comma, which likely disrupted the settings. While we don’t have sufficient information to identify a specific issue, implementing restrictions on user account creation could help mitigate any potential problems. I advised the individual that they could simply use their first name, as there are only about ten users on the server, so I wasnt too worried about overlap.

Thanks for the update!

1 Like