They need to go to the Edit Profile page and select the group badge they want displayed:
So, I'm using Lavender with some CSS tweaks. Nothing major, but when I make a new post in a topic, until I move away from that page or refresh, I get this:
I've looked through the source etc, can't see anything missing their closing tags...
**tap tap tap** this microphone on?
Happens here too. Note the last posts favourite button.
Glad I'm not the only one who saw this - no CSS tweaks on my site - occasionally happens on mobile as well.
People on my forum have noticed it too, I've not seen any code missing closing tags.
Considering my forum is completely stock, it should be something in the official code causing it.
Not sure where to start rooting for it though.
@a_5mith Yes, that sounds smart. That must be it. It's odd how it replaces the • character though - perhaps something with the encoding?
With all the posting we're doing, I doubt they would even see the notification
@Albus Only thing I can see it being is that
<!-- IF !reputation:disabled --> isn't being calculated quickly enough.
• has some weird alias as
• outside of the disabled rep might do it...
You could be onto something about relocating the
• to before
<!-- IF !reputation:disabled --> since it seems as if
• would be present, even if reputation was disabled as a separator from the post buttons and the favorite button.
@Albus Also noticed in my screenshot that the upvote is slightly darker than the downvote. Whatever that signifies.
EDIT: It signifies that you can't click the upvote button. Just gives you text input icon. downvote gives you the error of not being able to vote for own post.
Working on a fix it's not related to the
@a_5mith Almost as if the darkness typically applied to the bullet is being applied to the upvote, or first part of the reputation.
Either moving the
• will fix this - or we're putting too much thought into it.
@baris Awh maan, thought I was on to something.
@baris the ninja.
Well, at the very least we get some closure - even if we were wrong.
Update to https://github.com/NodeBB/NodeBB/commit/9fbd535b79acf8972d5b8caf1ab5386a18042325 that should fix the issue.
@baris Confirmed fix. Thanks.
Has this site been updated yet? Issue just occurred on mobile.
No this site isn't updated yet.