Thanks for updating in the future 
4 Likes
Many thanks for this great theme component 
We also use the Babble plugin on our site. Unfortunately, the badge icons show up there too, which makes quite a mess out of the chat. Any chance you could deactivate it for Babble?
Edit: I could hack it with this css, so at least the badge icons are a little more contained:
.poster-icon-container span.poster-icon img {
height: 1em !important;
width: 1em !important;
}
2 Likes
I’m seeing an exception coming from this theme component.
Source: https://github.com/tshenry/discourse-post-badges/blob/master/common/head_tag.html#L26
4 Likes
Hmm, I’m not immediately able to repro. Can you provide a little more context on how you’re triggering the error? Are you logged-in when you get the error? I assume the site is up to date? Is this a dev environment or production? Anything else that’s noteworthy?
1 Like
This is actually on my site, Angus was trying to help out because this exception is causing a problem with his multilingual plugin. I’m on 2.5.0.beta1, production environment with quite a few plugins and customizations. I’m not sure what steps to take troubleshooting from here.
2 Likes
Thanks for the clarification 
It definitely gets tricky as you add more and more plugins and other customizations from various sources.
The implementation of this component is certainly not my favorite… At the time of building it, I had to work around the limitations the best I knew how. I’m crossing my fingers we’ll get something in place will allow for a much more robust solution, but I’m not sure if/when that will be.
In the mean time, I won’t be able to guarantee this component will “play nice” with other customizations. Your best luck would probably be hiring someone from the marketplace to convert it into a plugin that’s properly serializing the required badge information.
5 Likes
Sorry for being brief in my last message. You can repro it with no other customisations if you disable the basic badge and create a post with a new user. The code assumes that every user has at least one badge.
Here’s a fix: https://github.com/tshenry/discourse-post-badges/pull/1
6 Likes
This is nice!
Would be great to have something like this in core or as an official plugin 
4 Likes
Agreed! This is the most indispensable non-official plugin I have installed. We use it, along with titles, to denote special responsibilities in our group, for example “Liaison” and “Area Leader”. Users really do care about having their bling prominently displayed.
5 Likes
Thanks for the PR @angus. It has been merged!
In other news, this component has been transferred into our official repository 
@joffreyjaffeux will be taking care of the long-overdue refactor this component has needed. Expect some updates in the not-too-distant future
13 Likes
That’s awesome!! Well done all
1 Like
Hi thank you very much for this awesome addon!
After adding Country Flags plugin we are having a spacing issue.
Is there css coding that could be used to correct this below
SOLVED!!
Using code example here was able to create a fix.
.nationalflag-post { width: 16px; margin-right: 3px }Result
3 Likes
I was wondering though what is the post badge identifier to use to modify position and sizing?
1 Like
You are going to need a fairly specific selector for this one:
.topic-meta-data .names .poster-icon-container span.poster-icon {
font-size: 16px;
margin-right: 3px;
}
Friendly suggestion - I would look into how to use your web browser’s inspector to find the CSS selector required to style an element (here’s a guide for Chrome for example).
4 Likes
Thank you very much. Have been using Firefox but recently a good friend reccommended switching to Chrome or Vivaldi as it has better inspect element.
3 Likes
Doesn’t work for me, too.
4 Likes
I see where the issue is. Thanks for the reports. I’ll try to get a fix in the next 24hrs.
Edit: it should be fixed now @tpetrov and @Anatolia. Let me know if you still have any issues.
7 Likes
There isn’t an update yet and still same.
Ah, I think I know what happened. We moved the repo over to the official Discourse GitHub organization, but the version of the component you installed is still pointing to the original repo. I believe there are supposed to be automatic redirects to ensure everything still works. Sometime after it was transferred, I created a fork which may have compromised the redirect.
I just deleted my fork. Can you try updating again to see if the redirect kicks back in? If that doesn’t work, I would recommend re-installing the component from the new repository link.
6 Likes