I am not against experimenting with adding a tiny avatar, but I would like to see the experiment in a plugin first. It is pretty straightforward to add.
I agree that option (perhaps as global setting) to display mention as @sam OR as Sam Saffron would be really great.
With the same formatting as mentions now have, but displaying full name instead of @handle
So, you guys allow for SSO logins, presumably to allow for companies, anong other entities who maintain master employee/user lists to login with ease.
The issue I’m running into here is this. We have 4500 employees. Most don’t know each other. While tagging by typing name in works perfectly fine, the username displayed is a 5 digit employee #. So now all people see is comeone tagging a 5 digit #
Can you guys write/enable a user option that simply displays the Full Name field in lieu of @username please!
You allow a user option to select the Full Name displayed first in a thread reply with username to the right. A simple visual switch.
I totally get the purpose of using a “twitter” tagging model, but it is severely aggravating for large professional/educational institutions to use. Please, please make an option available. In any means.
It’s not even in a paid hosted/supported version, so you’re missing out there on revenue for large organizations who might otherwise use this.
In my case, I’m trying to “sell” it to my board to adopt discourse. I’m sure they won’t like this missing capibility
Who decided the username had to be a 5 digit number? That’s a bad decision.
It’s quite common from what I have seen in larger organisations to have their AD logon use their payroll or ID number in order to logon rather than names. Not necessarily 5 numbers however. For example my last organisation my login was B3293016 - would be difficult to distinguish who that is if they then used SSO to check against that login and use it for discourse username and mentions.
What @mikechristopher said. The 5 did fit # is our employee I’d. Technically it’s 6, but the zero at the beginning is left off as we haven’t reached numbers greater than 100,000.
Bottom line, again having the feature I described will give corporate/enterprise clients a lot better usability.
Had you not integrated SSO, I’d understand being reluctant to allow full name tags vs username. But you made SSO available, this is a logical next step enhancement
I am not against adding this kind of option, but at the moment none of our paying customers need it so I cannot prioritize it.
I would probably recommend building this as a plugin first, this is something I would consider building if an enterprise customer funded it.
@mcwumbly have you had any luck with the CSS route?
Haven’t tried it, sorry. Just threw out the idea, but this isn’t something I’ve felt the need to explore too deeply personally.
Just to beat this dead horse a bit more, one of the barriers we’re having in our group is that people get super easily confused by the usernames. So right now, they have no problems making mentions, but when reading, they often don’t know who the mentioned person is. As such, in our use case, @cpradio (Jim Smith) would be ideal. The user would type in the @mention (let’s say @cpradio) and it automatically turns into @cpradio (Jim Smith) for others to read.
This would be just like the username mentions by each of our posts.
Has there been any movement here? It’s annoying to have to click on a username to figure out who the actual person is. And trying to move from Facebook Groups to Discourse is a pain when don’t get to see full names by default. I don’t think uniqueness is really the problem that people think it is from reading previous comments, as, once again, you can use usercards to differentiate if that’s the case. I’ve already changed the site settings to prioritize full names in UX…
I made a quick script that does this. I put it in a component, in the </head> section, and it works. It could definitely be improved upon, but here it is.
<script type="text/discourse-plugin" version="0.1">
var decorateAtMentions = function($post) {
$post.find("a.mention").each(function() {
var $elem = $(this);
var username = $elem.text().substr(1);
var data = Discourse.User.findByUsername(username).then(function(user) {
var avatarurl = user.avatar_template.replace("{size}", 18);
var realname = user.name;
$elem.before("<img src='"+avatarurl+"' title='"+realname+"'>");
$elem.attr("title", realname);
$elem.after("["+realname+"]");
});
})
}
api.decorateCooked(decorateAtMentions, {id: 'decorate-at-mentions'});
</script>
The title in the img tag is a potential problem if a name has a single quote character, so it needs to be done “the right way” (myself, I’ll probably remove it since I don’t really like it that much).
I wanted to change the link text, instead of appending the real name at the end, but unfortunately that breaks the click handler for the user card (since it apparently relies on the mention text to load the name) and I didn’t want to go down that rabbit hole.
훌륭하네요. 초보자를 위해 제 discourse 인스턴스에 실제로 추가하는 방법을 단계별로 알려줄 수 있을까요? ![]()
이미 가이드가 있으니, 아래를 읽어보세요.
그리고 첫 번째 테마 컴포넌트를 만들어 보세요.
@nachof 작동하는 방법을 찾았습니다: Use fullnames for mentions · GitHub component:user-card-contents에서 _show()를 오버라이드하는 방식입니다. 앞에 언더스코어가 붙어 있는 것은 오버라이드하지 않는 것이 좋다는 의미일까요? 하지만 잘 작동하는 것 같습니다:
아마도 $target에서 사용자 이름을 선택적으로 가져올 수 있는 진입점이 필요할 것 같습니다. 어쨌든, 이는 제 관점에서 더 넓은 커뮤니티에 배포하는 데 정말 큰 장애물이었습니다. 이제 앞으로 나아가는 때입니다 ![]()
정말 놀랍네요! 저는 소프트웨어 개발자가 아니라서 jessicah님이 만든 것을 제 디스코스(Discourse) 사이트에 어떻게 추가해야 하는지 도저히 알 수 없었어요. 이 URL을 사용해 git 저장소로 설치하려고 했는데, 이것이 디스코스 테마인지 확인하라고 물었습니다. 어떤 단계를 거쳐야 할까요?
UX에서 새로운 테마 컴포넌트를 생성한 다음, 해당 내용을 테마의 head 태그 부분에 붙여넣습니다.
100번째나 같은 이야기를 꺼내는 건 죄송하지만, 올바르게 설치했는데도 사용자 카드가 표시되지 않습니다. 2년 전부터 이어져 온 이 문제에 대한 해결책이 있을까요?
다시 프로그래밍하는 데 공을 들이실 가능성은 낮다는 걸 알지만, 혹시 커뮤니티에서 누군가 도움을 주실 수도 있을 것 같아서요.
솔직히 아직 이 지침들이 잘 이해가 되지 않습니다. What makes a successful volunteer Discourse sysadmin? 에 대한 도움은 정말 큰 도움이 되지만, 아직 해당 자원봉사자를 찾지 못했습니다.
그동안 @jessicah 님, 혹시 Customization > Theme component 에 게시할 수 있는 테마 컴포넌트로 만들어 주실 수 있을까요? 아니면 다른 누군가가 작동하는 테마 컴포넌트를 만들 수 있을까요?
@debryc님과 @OverseersMight님,
여전히 관심이 있으시다면 ![]()
