I used it in that way for quite sometime until it started to fall apart.
I ended up starting my own rocket chat server. Babble was good enough to make chat a staple on my site. Rocket chat runs so much smoother. It’s so good though that it’s probably going to decrease forum usage, but it’s too late for me to put that genie back in the bottle.
Hey guys, I’ve resolved the spinner issue. Update to the latest version of the plugin and it is working again. You can test it out here: https://try.thepavilion.io (there seems to be a slight style issue with the babble icon on that site, but the functionality works fine; it’s probably a conflict with another plugin or theme)
Respond to other users of the plugin here in this topic with links to those wizards, and the documentation when… you write it
If maintaining this plugin was more a matter of clearing a clearly defined list of issues every once in a while, with good descriptions, logs and associated screenshots etc, then that’s a much easier proposition time-wise.
Also, if you submit a bug reports via thepavilion.io/w/bug-report, I will now get automatically assigned to it, and it’ll make my stats look bad if I don’t close it…
So I’m much more likely to action it sooner if you submit a full bug report, with logs, screenshots and good descriptions.
I’m still going to have this plugin on my list of open source assets to find a new owner for, however if collectively we can do the above, we’ll be able to at least maintain it in a decent state.
Thanks for fixing the issue with the constantly spinning wheel icon in the chat when you post something. The only bigger outstanding UX issue I can think of right now is that the icon letting you know there’s a new message in the chat never goes away, even after reading all messages. @TheBaby5 gave the high-level overview of that one.
I just did a quick test and @ninermac’s bug report from October 20 doesn’t seem like an issue on our Discourse install.
I see some minor items in this giant thread that could still be addressed, but they’re not mission critical from my perspective. For example, @Dev_Work has one from October 20 about a missing translation.
Wait a moment. Are you saying, time allowing, that you’re going to fix future Babble bugs out of the goodness of your heart? Because that’s what I think (or maybe just hope) you’re saying.
We’ve already had a lot of generosity with Babble over the years with James maintaining it well beyond when it was practical for him. I’m all for more generosity and I give it myself in many ways and many places, but I want to make sure you/we are setting the right expectations here.
Me too. I’m no developer and I mostly orbit around the Discourse ecosystem instead of drop into the gravity well of it. But I’m all about the open source ethos and finding the people who will make communication better and easier for the many folks who use, love, and can’t live without Discourse (that’s me!).
Whatever you do from here, Angus, you’re a total .
Pavilion, our non-profit cooperative, exists for three purposes (these are taken directly from a new set of articles of association I’m in the process of registering)
provide opportunities for work, education and related services to providers of services and products to online communities;
facilitate the provision of services and products, and the development of open source technology, for the benefit of online communities; and
pursue socioeconomic diversity amongst the recipients of the benefits and opportunities in objects (a) and (b).
This is what we do We’re currently building a new website that explains this better (and I’ll be releasing a big new open source landing pages plugin for discourse alongside it).
Thanks for these notes. Ideally, if those folks could submit bug reports: thepavilion.io/w/bug-report, then I’ll be able to action them systematically over time.
We need you just as much as a developer . Here’s some Babble knowledge management that needs doing:
Update the first post in this topic to better reflect the current state of the plugin (it’s a wiki). Take a look at the custom wizard plugin OP for an example structure.
Create a “How to setup Babble” topic in the knowledge category I set up: Babble - Pavilion.
Create a “How to customise Babble” topic in that category. @REALITY That would be the place for your useful CSS suggestion, which unfortunately, will otherwise be lost in the mega-topic.
Don’t worry about writing “the wrong thing”. If you make a mistake, or what you write is unclear, others (such as myself) will help you correct it. That’s the beauty of being part of an open source community.
Please file a full bug report here and I’ll address it soon: Bug Report. I know that may seem pedantic, but it really does help! If we break the cycle of using this topic as a catch-all place for all issues, things will get done more efficiently.
Trying to file a bug report. I’m trying to create an account on the Pavilion site with a social login (Google) but end up in a login loop. Do I need to create a local account to log into the site and file a bug report?
This has a massive lack of any sort of feature and I was fine with that, working great, but messages hang constantly especially if they’re more than like two words. Is there a good alternative to this? I’m aware of the one that connects with third party chat programs and such but just looking for a chatbox sort of thing for certain user groups. This obviously isn’t worth it with the hang ups
I have Babble installed but no longer use it, so it’s disabled. I wouldn’t care whether it was installed or not, except that my site is now broken in either case.
If I uninstall it, it breaks the groups page at /g:
If I leave it installed but disabled, it breaks our custom digests. Admittedly this is being called by our discourse-506investor-digest-plugin, but it seems the NilClass is in babble/app/models/topic.rb.
Job exception: undefined method id’ for nil:NilClass`
/var/www/discourse/app/models/post.rb:99:in `block in <class:Post>'
activerecord-18.104.22.168/lib/active_record/relation.rb:412:in `block in _exec_scope'
activerecord-22.214.171.124/lib/active_record/scoping/named.rb:192:in `block in scope'
activerecord-126.96.36.199/lib/active_record/relation/delegation.rb:66:in `block in for_mailing_list'
activerecord-188.8.131.52/lib/active_record/relation.rb:407:in `block in scoping'
/var/www/discourse/plugins/discourse-506investor-digest-plugin/plugin.rb:24:in `block in execute'
/var/www/discourse/lib/distributed_mutex.rb:33:in `block in synchronize'
/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
/var/www/discourse/app/jobs/base.rb:221:in `block in perform'
mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:37:in `block (2 levels) in initialize'