Babble - A Chat Plugin

Just tried the plugin on a fresh install, and with the graceful theme the bullhorn button appears… but doesn’t have any background so it’s hard to see. It was happening because I had background: transparent set on the global .btn class.

I added some styles to fix it

31%20PM

@Genyus, if you update the theme the button should be back…

5 Likes

I applied the update and the icon is now visible. Thanks for the swift fix!

2 Likes

Would it be possible to have users disable display of the icon, perhaps in preferences? I’m already starting to see complaints.

Adding user preferences is a bit trickier than I’d like, but there’s a couple user preference related requests so I’ll likely get to it at some point.

One approach for today might be to create a theme component with

.babble-sidebar-component,  #babble-icon { display: none };

in it, and allow users to select their theme based on whether they want Babble to appear or not
(Ie, you could have Vincent (with chat) and Vincent (without chat) as selectable themes)

2 Likes

So, I’d love if you could remove them from RSS feeds, especialy in my case from discourse.url/posts.rss feed, as we use it to display latest posts on our homepage, and would like to exclude chat messages from them :wink:

I was wondering… If I understand correctly, user-to-user mechanism at this moment works this way:

  • creates new user group
  • creates for it new Babble channel
  • messages on this channel
    Wouldn’t it be easier to utilise built in Discourse PM mechanism?
    Don’t get me wrong, I’m don’t know tiniest bit of Ruby, it just seems logical :slightly_smiling_face:
    Cheers ant thank’s for all the good work!

There’s another plugin that does exactly this:

I am well aware of Angus’s plugin, i use it with pleasure, but thanks :slight_smile:

1 Like

Hey All! Sorry if this has already been answered, but if I wanted to add a hyperlink that would open babble, could anyone give me some direction?

Line wrap seems to be hit and miss. One user who tried it was seeing correct line wrap as he typed, but after hitting return they were only partly visible. I thought this might be a result of having a particularly long user Name, but this was unrelated. Strangely, his posts started line wrapping correctly after 5 or so posts.

Could you create a github issue here with a screenshot of the unwanted behaviour?

Okay I’ve got a fix for this and will push with the next update.

We already have two completely separate sets of permissions for determining whether you can see a chat, one for groups and one for categories. It’s about at the edge of unwieldiness that I’d like to see. So I opted for re-using the existing group logic, rather than having to go down three paths to determine whether you can view / respond to a topic or not.

2 Likes

Did this ever get sorted?

Thanks, that makes sense :slight_smile:

Alright, I’ve been chipping away at some things today. Here’s a list of stuff I did:

  • Added individual user settings for disabling Babble and enabling notification sounds (default off)
  • Removed chat posts from search results and rss feeds (this change will also prevent people from receiving badges based on their chat activity)
  • Fix for user being unable to log in on latest stable
  • More assertive CSS to make it harder to steamroll Babble from within theme components
  • Moved the audio tag, which I believe has fixed the OAuth login trouble (@Genyus could you help me confirm this? I can login via Facebook on the sandbox just fine at the moment.)
  • Add fix for long words not wrapping correctly sometimes
  • Pushed a locale update (yay German and Dutch!)

Let me know what other requests you have?

4 Likes

Great work! I noticed that every chat that gets sent in Babble shows up in the latest topics on the sidebar plugin.

I’m the maintainer of the sidebar blocks plugin, and, sad to say, but this is less of a Babble issue and more of a “Discourse Sidebar Blocks” plugin issue. (Unless this is something that changed recently, but I doubt it…)

1 Like

Sorry for the delay, James. Tried to test this yesterday but was blocked a coincidental bug in Discourse itself:

With that issue fixed, I’ve re-tested but am still seeing the same behaviour.

It seems like there’s something wrong with your setup, for example visiting community.froware.com/babble/notification.mp3 results in a 404, whereas discourse-babble.com/babble/notification.mp3 sends the notification audio file. Any reason you can think of that this might be the case? What other plugins, or customized code on the server side, might be interfering?

Apologies, when I was testing before, I disabled the plugin to see if it still behaved the same way as previously — whereby it tries to load the .mp3 URL, but as the plugin is disabled, it renders the 404 page instead of downloading the file. I’ve re-enabled it now.

Hm, so the bug exists when Babble is present, but disabled, and someone logs in with OAuth?

I’ve just pushed a fix so that the notification file is not loaded unless a) Babble is enabled b) there are chats for the current user to participate in c) the sound option is enabled for that user, which I’m hoping will clear up most of the use cases here. We still have to check though that users who are loading the mp3 are able to sign in with OAuth. :confused:

1 Like

Correct. If the plugin is enabled, then the browser downloads the .mp3 file on login. If it’s disabled, it still attempts to open that URL, but it fails and renders the 404 page instead.