Hello 
You can order it to the first place with adding this css to a component Common/CSS section.
#user-card {
.metadata {
.last-seen-metadata {
order: -1;
}
}
}
5 Likes
Thank you for the code. I applied it, cleared cached, and reloaded, but the position didn’t change.
1 Like
Hmm it should work… 
Did you add it to the right place in Common/CSS and activate the component to the theme?
One more thing I can think is you have an older version of Discourse and this code might not work.
I updated the code above!
1 Like
I added it as a component then added css
I don’t think it’s old as I’ve just downloaded it yesterday and installed it on my server.
Could you share your site url so we can check what is happening? 
You can send it in PM too if it’s not public.
Got it working! I just had to rebuild. Oopsie. 
CSS change doesn’t need rebuilding Just reloading of the forum in a browser.
2 Likes
I didn’t think so, but that’s the only thing that worked. Maybe a coincidence.
Me personally, it should be last post, and the last seen.
How do I fix this?
1 Like
Thank you for reporting this. I pushed a tiny update. The admin notice banner should go away when you update the component.
3 Likes
Component stopped working after latest update. No errors shown.
Version: 3.5.0.beta5-dev - (d564386066)
Can you make sure you are checking the user cards for accounts that have actually logged into the site at least once? If you can confirm that it is not working for any user, would you mind updating your Discourse instance and letting me know if it starts working after that? If it does, then I may try pinning the latest commit to this component to the newest core beta just to be safe.
2 Likes
Same here, but I’m on v3.4.6 (Stable channel).
Confirmed, it was working before this update, and it no longer works now for any user. I just updated my Discourse instance to v3.4.6. Would it be possible to make this updated Glimmer implementation only be installed for users on v3.5.x and offer the previous version for v3.4.x?
BTW thanks for this extremely essential component, it really should be in core Discourse. 
2 Likes
Thanks for the confirmation @rahim123. I’ve just added a compatibility file that I think should pin the component to the previous version (non-glimmer) for a site running a core commit that was made before 3.5.0.beta7-dev was released. Can you update the component and let me know if it starts working for you again?
2 Likes
It wasn’t finding the update, so I had to delete and re-install the component. It’s now working again, thanks so much for the quick response!
4 Likes