sam
8 juni 2016 om 05:14
1
I just added a site setting that allows you to prioritize full names as opposed to usernames in the UI.
When usernames are prioritized cause the site setting prioritize_username_in_ux is enabled you will see:
In card:
On user page:
In post stream:
prioritize_username_in_ux is disabled you will see:In card:
On user page:
In post stream:
I feel an @ symbol may be worth adding per:
This can be done safely via CSS, leaving it off for now.
Quotes inside the UX still pull in username eg:
We may look at making this switch to be fullname based when the setting is set.
18 likes
riking
8 juni 2016 om 05:37
2
Bug report: If full name is blankish, username is offset and not fully bold
1 like
sam
8 juni 2016 om 05:44
4
corrected per
https://github.com/discourse/discourse/commit/0e2d918b3b3807041126bc66d3e0d205d42c7820
Still abusable, but we might as well correct that server side by doing a trim on save that is unicode aware.
3 likes
sam
8 juni 2016 om 05:45
5
That is a can-of-worms to implement, same class as improving quotes. I may get to it, but not for this round.
3 likes
gerhard
9 juni 2016 om 14:06
6
I believe the username should be shown with @ by the default. It’s a lot less confusing.
And the username should always be visible. Don’t make me think.
5 likes
At symbol too noisy repeated all over the page. In the user card should suffice.
1 like
jerry0
3 januari 2020 om 03:06
8
This is working in almost all places, but not in email notifications.
So, in e.g. user card it looks fine.
But in email notifications full name is not prioritized:
(also I think only one of the two names need be hyperlinked, the first I guess)
2 likes
sam
3 januari 2020 om 04:19
9
@techAPJ can you investigate a fix for emails?
3 likes
techAPJ
20 februari 2020 om 12:20
11
Fixed via:
https://github.com/discourse/discourse/commit/f36719c1f5aac7e72e12f298cf9e23a2076ac17b
When prioritize_username_in_ux is enabled:
When prioritize_username_in_ux is disabled:
4 likes
techAPJ
20 februari 2020 om 12:23
12
Further simplified the styling to use same CSS for username and user-name. (notice the bold font-weight for username vs the normal for user-name.)
https://github.com/discourse/discourse/commit/7b92280b97ea483685040c6c5f8c23b3d8c9f0a2
4 likes
techAPJ
23 maart 2020 om 16:32
13
4 likes
I found a place where this setting doesn’t seem to be taking effect: the list of username matches on search results:
Geminiscp is the username and prioritize username in ux = true.
3 likes
debryc
2 december 2022 om 19:18
15
We just installed the experimental sidebar and chat. Can full names be prioritized in the Personal chat section as well if we disable prioritize_username_in_ux?
1 like
