Handle uppercase of username differently

Avatar
Ryann
  • updated
  • Completed
UserEcho decided to display the username with the first letter uppercase, even if the user set it lowercase in his profile.

For instance "john01" becomes displayed "John01" quite everywhere in the UserEcho pages.
This is nice, but sometimes this uppercase is forgotten (some missing cases have already be noticed as feedback before).
Since there is still some missing cases (for instance the username of a new post when you are notified by e-mail) I guess it would be more efficient to set the uppercase directly in the user name profiles than everywhere in the code for each display.
=> thus, usernames would always be displayed correctly and the same way.

Moreover, if you feel important to keep the username stored exactly as the user entered it (maybe lowercase) for instance for editing in the user profile, then UserEcho could save this "originalname" too, but beside the username which would now be the normalized form with uppercase.

Is it a good compromise?

P.S. Maybe another point of view would be to stop forcing uppercase and keep displaying the name as the user entered it, without forcing uppercase... I must admit I have no real preference, but just would like it to be harmonized.

How would you rate the customer service you received?

Satisfaction mark by Ryann 8 years ago

Thanks to have elected the third solution!

Add a comment about quality of support you received (optional):

Pinned replies
Avatar
0
Vladimir Mullagaliyev co-founder
  • Answer
  • Under review
Hello Ryann,
Thank you for your feedback.
We are deciding between:
1. Fix all places to get first letter to uppercase
2. Save data in Capfirst
3. Leave all names as is
Replies 6
Avatar
0
Vladimir Mullagaliyev co-founder
  • Completed
Quote from Ryann

Any conclusion?

Considering that this variability in forcing uppercase still occurs regularly:

  • most time the username is displayed with first letter corrected to uppercase
  • but for instance, in notifications e-mails this is never the case (in the text "post by xxx")

=> I guess the most "simple" and "user friendly" would be to keep the name as entered by the user, with no change at display time


(one more reason is that sometimes users in forum choose "aesthetic" uppercase for their pseudo).

Best regards.

We've disabled this feature. You will see the names as is.

Avatar
0
Ryann

Any conclusion?

Considering that this variability in forcing uppercase still occurs regularly:

  • most time the username is displayed with first letter corrected to uppercase
  • but for instance, in notifications e-mails this is never the case (in the text "post by xxx")

=> I guess the most "simple" and "user friendly" would be to keep the name as entered by the user, with no change at display time


(one more reason is that sometimes users in forum choose "aesthetic" uppercase for their pseudo).

Best regards.

Avatar
0
Ryann
Hello,
Great... Sometimes I wonder if the simplest (option 3) would not be the better... ;-)
Option 2 is also efficient. But really 3 or 2 sound better than 1 from my point of view.
Thank you for your attention, and thank you by advance for your choice!
Avatar
0
Vladimir Mullagaliyev co-founder
  • Answer
  • Under review
Hello Ryann,
Thank you for your feedback.
We are deciding between:
1. Fix all places to get first letter to uppercase
2. Save data in Capfirst
3. Leave all names as is
Avatar
0
Ryann
Another place where uppercase for the initial letter of the user has been forgotten:
simply the name visible on any UserEcho page, written up-right as menu to reach the profile :-)
Avatar
0
Ryann
BTW, I just noticed that the usernames in the RSS feeds have also been forgotten in this uppercase modification (compared to the names displayed in topics web pages).

Customer support portal powered by UserEcho