I’m seeing at least a few of my users’ cards appearing more than once… eg “andy1” and “blane” among others on this page:
update: Something funny is going on. I saw it in cognito on Chrome, but I don’t see the dupes logged in when using Safari. This is going to be hard to track down…
Hi Craig - thanks for the report. Looks like this is a problem with Discourse core - it happens even with the user cards component disabled.
The root of the problem is that all your users currently have ‘0’ values for the metrics, and our sorting was inconsistent. I’ve opened a PR to fix the issue, and will get it deployed to your site once it’s merged. Technical details are in the PR if you’re interested
That’s fixed, and I’ve deployed the core change to your site @craigconstantine. Let us know if you’re still seeing any issues.
That’s fixed, sorry for the long wait! Update the theme component in your admin dashboard and things should look good on light/dark themes
How would I go about changing the default sort to “visits” rather than “likes received”?
Thanks!
hi! this component is great! We found though a weird behavior while showing the number of followers
You can check yourself here: LibreCV
I’m afraid that’s not possible at the moment
“Followers” isn’t a concept that exists in Discourse core, so I guess you must be using Follow Plugin 👨. This is something that will need to be fixed in that plugin.
Indeed, I use that plugin - would be great that can be fixed 
I could be wrong but believe the repetition of this card breaks its own Plugin Outlets, rendering them useless, but worse, they act unpredictably (or predictably bad?) if you have a dependent Theme Component or Plugin installed. I think it is essentially spamming the template with multiple, identically named plugin outlets?
Can we find a way around that?
I don’t think multiple copies of the same plugin outlet should necessarily be an issue. For example, there are plugin outlets on every single row of a topic list, and things work fine there.
What error/issue are you seeing?
That’s encouraging.
So a different model is being passed to each instance?
Currently the same data seems to be repeated on each card
Yeah the user object should be different for each one… in theory
Which specific outlet are you using?
Yeah, I’m not yet convinced that’s actually happening, but would be delighted if I were wrong.
On Directory:
On solitary card clicked up from Topic list:
Perhaps I’m missing a best practice here, not sure.
I suspect it’s being caused by this:
I’m not entirely sure what this code is trying to achieve… but it looks like it’s looking up .card-content .metadata, and then appending itself? to every matching element 
If you use a standard ember computed property, I think things will work much better.
Aha! That’s a very helpful line of enquiry, thank you. I’ll take a look at refactoring that.
User Card Directory seems to have lost the ability to filter by username. When the component is enabled, typing in the search field has no effect.
When the component is disabled, filtering works as expected.
I am able to replicate this issue. Filtering by group works, but filtering by username has no effect.
Hey. The user cards are beautiful. Thanks for making this.
Can we add an option that hides the user statistics?
I’m seeing—I’m guessing here—something wrong with string translations?
Thanks @craigconstantine, we have a fix in the pipeline. I’ll let you know once it’s merged and ready for you to update.
