I’m not sure what exactly is doing it but a(ny) CSS code I use to do this seems to turn on and off at random, I don’t know if it’s from an update, some setting, etc… The one I’ve used for the longest is .topic-post .Veeps a { color: #66FF00; } With “Veeps” being my Custom Group. It was working as of either yesterday or the day prior but I noticed today all the colors except the ones linked to specific usernames are back to default, on every theme. I made a new theme and wiped all modifications to try and literally none work. It works perfectly fine with premade groups like “admin” “staff” moderator, but I can’t get any to trigger for custom groups. I’ve made sure it’s set to Primary Group, made it the only group they were apart of, tried on different custom groups (“Owner”), nothing. Now if I apply it to specific usernames it works fine, but it’s tedious to have to make 100 separate entries for individuals, that doesn’t update if their group changes. span.username.staff a { color: #00A9DB; } Works, but also not for Custom Groups. I know it WAS possible to make Custom Groups work because for years it’s worked for multiple (except when it doesn’t). Is there some better CSS to use, or some setting that I’m inadvertently messing with? I installed GitHub - discourse/discourse-groups-css-classes-in-body · GitHub and now I’ve gotten div.topic-post.group-Veeps div.names span.username a { color: #8A2BE2; } To function how I won’t, but I haven’t installed this (or been using that CSS) for the last couple years so it doesn’t help me understand what exactly stopped working/what to fix, just hitting the nail in with the drill.

Hello, There was a change yesterday DEV: add title class name, prefix username class (#19482) · discourse/discourse@b1e0836 · GitHub so now you have to add the group-- prefix to the group name in css. For example: .group--Veeps.

Yes, sorry for the inconvenience but the previous way we were adding the group class name was a little error prone… it meant that any group name that happens to match a class name in our CSS would cause layout issues. For example, a group named “hidden” would add the class .hidden, which would hide usernames. Adding the group-- prefix avoids this issue, and this shouldn’t need to be changed again in the future. So you should just need to update .Veeps to .group--veeps

[image] Don: Hello, There was a change yesterday DEV: add title class name, prefix username class (#19482) · discourse/discourse@b1e0836 · GitHub so now you have to add the group-- prefix to the group name in css. For example: .group--Veeps. [image] Kris: Yes, sorry for the inconvenience but the previous way we were adding the group class name was a little error prone… it meant that any group name that happens to match a class name in our CSS would cause layout issues. For example, a group named “hidden” would add the class .hidden, which would hide usernames. Adding the group-- prefix avoids this issue, and this shouldn’t need to be changed again in the future. So you should just need to update .Veeps to .group--veeps Thank you for letting me know, I feel slightly less stupid that I somehow broke something trying to fix something else as is often the case! I’ve played around with a few different cases and they all work fine and I’ve been able to work it out with this information. Does it require the use of GitHub - discourse/discourse-groups-css-classes-in-body · GitHub to still use custom Primary Groups in this fashion I was asking about, or is it unnecessary? I possibly misunderstood the purpose of that plugin in the first place and it was never required for what I was doing; I just removed it from my test theme to see if the custom primary group codes were still trigger, and they do, so it seems like it’s not needed…but I would rather be sure before I just turn it off and find something unexpected down the road.

[image] Kartoon: Does it require the use of GitHub - discourse/discourse-groups-css-classes-in-body to still use custom Primary Groups in this fashion I was asking about, or is it unnecessary? The primary groups are present without it, so can be targeted with CSS. With the theme component installed you can also target non-primary groups too. :+1:

I didn’t understand which code I use, maybe the translation is out of context so instead of me using this div.topic-post.group-Veeps div.names span.username a { color: #8A2BE2; } I use this div.topic-post.group-- Veeps div.names span.username a { color: #8A2BE2; } I don’t understand what should be put in the code? it’s just the -- @Kartoon @Don @awesomerobot

Hello, It should work like this :arrow_down_small: .names span { &.group--GroupName a { color: red; } } But I’ve made a quick theme component for this now. :slightly_smiling_face: Here you can simple set up this. groupname;color [Screenshot 2023-01-14 at 21.07.53] https://github.com/VaperinaDEV/name-color-by-group

I’m probably not the best one to ask as I can make things work but not necessarily explain why. But what I’m currently using and works fine .topic-post.group-Veeps div.names span.username a { color: #66FF00; } Obviously swap “Veeps” for whatever usergroup you have that’s just what mine is named. .names span { &.group--Veeps a { color: red; } } As mentioned above also works I just swapped it for what I had. I’ll probably install the plugin he just posted though for convenience either way

I’m having the same problem too, I don’t know what’s wrong, impressive that even using the competent theme or the code, because the members’ names don’t change color, I even used the cogido and the component theme in a raw theme without any css or changes and it doesn’t change anything about the colors of the title I just noticed something intriguing, if I put someone in the group as the owner, the change code works and the colors of the names of the members that I set as the owner are changed, but the members who are not the owners do not change @Kartoon @Don @xebiyen

CSS Change username color for entire Custom Groups, works sometimes then doesn't?

Development

JammyDodger December 17, 2022, 6:14pm 5

The primary groups are present without it, so can be targeted with CSS. With the theme component installed you can also target non-primary groups too.

Topic		Replies	Views
CSS username colors only working for admin/moderators? Development css	17	518	July 6, 2024
Unable to change Usernames a specific color based on the group they are in Product Support groups	2	154	January 8, 2026
Gradient username colors dont work, why? Development	2	585	January 15, 2023
Changing username colors Product Support	3	2985	May 27, 2019
Change Default Username Color Product Support	1	735	May 9, 2022

CSS Change username color for entire Custom Groups, works sometimes then doesn't?

Related topics