I can’t see any problem in the screenshots. What exactly are you expecting that is currently not working?
3개의 좋아요
Not Card. Table set toggle.
1개의 좋아요
As mentioned above, if you could take the time to be more descriptive in what issue you’re facing it would save everyone the effort of trying to puzzle out what you mean. Just a few complete sentences describing what you’re trying to do, what you’re expecting to see, what button you’re pressing, and maybe a screenshot or two with the relevant parts highlighted.
If you cannot put that minimum effort in, then I’m afraid this is not the right place to get the support you need. 
It seems what you’re trying to say is that this button is not changing the view from card to table as you expect:
5개의 좋아요
This comment isn’t meant to be a fight, I’m just saying it like it is.
-
Unfortunately, I didn’t come to this post looking for support.
1-1. If I was looking for support, I would have made a separate post with the support tag. My goal was to report that fact to the component author as a bug. I think the component author would have easily figured out what I meant because he implemented the functionality himself. -
This doesn’t mean you’re wrong. Obviously, if I’m looking for support, I think like you said, the more specific the better.
-
You say I didn’t do the bare minimum, so I wouldn’t have tried to respond by taking screenshots, hosting images, etc. I think the display is close to sense. Even when I look at other comments, other users don’t always indicate the instructions.
-
I was able to mark it anyway, but I forgot, but I thought you could tell by looking at the size of the photos that they were different, and since you uploaded two photos, I thought you would have accepted that they were most likely different photos.
1개의 좋아요
I’m sorry @Truest, but these comments are below the minimum standard of what’s expected to either report a bug or ask for support.
As I think has been demonstrated by the ensuing conversation, if you had included more description in your initial post then you could have saved people a lot of time piecing together what you meant.
Please be more mindful of this in the future. 
11개의 좋아요
I’m enjoying this plugin, and appreciate all the work that’s gone into fixes and added features.
In our case (lots of new users stingy with Likes) the default timeframe & the ordering by likes_received results in dormant users with very low engagement appearing at the top of the page. They typically received a couple of Likes way back when, and haven’t been back.
I know it’s not meant as a leaderboard, but I’d rather order cards by, say, days_visited.
So I’d like to second this earlier request…
5개의 좋아요
I think choosing another default ordering is already possible.
I think the first column is used for that. So, when you move “days visited” there, it should work.
Regarding the time span: how do your users visit the directory? Would it help to edit the link in the sidebar so it takes them to /u?period=yearly instead of /u?
5개의 좋아요
I’m puzzled, as it does appear to be doing that here on Meta.
I tried on my site, but it literally just repositions the columns in the table view.
If I re-order by clicking a different column in the table view, then switch to card view, it retains that order until I leave the page and return. A fresh visit to either the card or table view orders it by likes_received again, no matter what order the the columns are in.
Unless maybe there’s some scheduled job that needs to run, to store the change..?
(I know a partial workaround would be editing the Users sidebar link to /u?cards=yes&order=days_visited but it’d be nice to have config options for default timeframe too.)
EDIT: either I missed your closing line, or you added it while I was composing. Yes, /u?cards=yes&order=days_visited&period=yearly does the trick. (And looks like /u?cards=no&order=post_count is what’s happening on Meta.) I’m happy with that for the moment! But still, admins might like some added config options.
7개의 좋아요
I’ve been very happy with this plugin, once I understood a few details!
Just one nagging issue: background images on user cards usually fail to load when first accessing the page. On refresh, the background images load. This is independent of color scheme or light/dark mode, and occurs across browsers on Windows & Linux. I don’t see any clues in the console. In safe mode with plugins disabled, it still happens.
I’d love to see a tweak to address this, as users aren’t going to refresh the page & learn that background images are even a thing.
3개의 좋아요
5 posts were merged into an existing topic: Message button is not hidden in mobile view
Hi, this TC still shows about only 40 users on my site which has more than 700 users. Is it only me ? 
1개의 좋아요
2 posts were split to a new topic: Users created via sso not showing up in user directory
저도 같은 증상입니다. 무한 스크롤 기능을 말씀하시는 거라면, 3.6.0.beta3-latest 버전에서 깨졌습니다. 잠시 살펴본 결과 이 버전의 현대화(modernization) 커밋과 관련이 있을 것으로 추정되며, 플러그인 업데이트가 필요할 수 있습니다.
참고로 기본 디렉터리에서는 무한 스크롤이 여전히 작동합니다.
1개의 좋아요
이 테마 컴포넌트를 정말 감사드립니다. 이제야 발견했는데 정말 반가운 존재입니다.
한 가지 질문이 있습니다:
사용자 프로필의 “자기소개” 내용이 카드에 표시되는 것은 우리 커뮤니티에 매우 유용합니다. 그런데 기본값인 2줄보다 더 많은 내용을 표시할 수 있을까요?
어딘가에서 이 부분을 조정할 수 있을까요?
혹은 대안으로, 카드를 클릭했을 때 링크가 /u/xyz-name/preferences/profile로 연결되도록 할 수는 없을까요?
다른 사용자의 설정은 볼 수 없는데, 왜 사용자 카드에서 그 설정 페이지로 링크를 걸어야 하나요? 제 카드가 https://meta.discourse.org/u/moin으로 가는 대신 https://meta.discourse.org/u/moin/preferences/profile로 가는 데 어떤 장점이 있나요?
감사합니다! 유효한 질문이며 좋은 정보입니다. 프로필에서 “확장”을 클릭했을 때 일어나는 일은 놓치고 있었네요. 하지만 “확장”된 상태로 기본값을 설정하는 방법이 있는 것 같고, 저는 그걸 모르고 있습니다.
힌트를 주실 수 있을까요? “자기소개” 부분이 접혀 있지 않으면 정말 유용할 것 같습니다.
본인 프로필을 보고 있지 않는 한 ‘확장된’ 상태가 기본값인 것 같습니다. 본인 프로필에는 뭔가 특별한 마법이 있는 것 같아요. 예를 들어, 기본적으로 /summary 대신 /activity로 이동합니다. 제 사용자 카드가 다른 사람들의 것과 다른 곳으로 이동하는 것이 종종 혼란스럽습니다.
여러분의 경험도 그런가요?
1개의 좋아요
음, 제가 아직 초보라서 이 사실을 몰랐네요. 다시 한번 감사드립니다. 이제 제 문제는 모두 해결되었습니다. 물론 Discourse와 관련된 문제들이지만요 
2개의 좋아요
로컬 시간 표시에 대해 콘솔에서 비권장(deprecation) 경고가 표시됩니다:
deprecated.js:52 DEPRECATION NOTICE: Setting timezone property of user object is deprecated. Use user_option object instead [deprecated since Discourse 2.9.0.beta12] [removal in Discourse 3.0.0.beta1] [deprecation id: discourse.user.userOptions]