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

[Kartoon]

@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.

@awesomerobot

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.