I can’t see any problem in the screenshots. What exactly are you expecting that is currently not working?
2 Likes
Not Card. Table set toggle.
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:
4 Likes
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.
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. 
10 Likes
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…
3 Likes
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?
4 Likes
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.
6 Likes
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.
1 Like