This is amazingly great in so many aspects. It changes a lot from the “me, me, me!” we can all witness sometimes in life. I give you a virtual hug, Angus: (safer at the same time, these days )
Thanks so much for taking this plugin on! Much appreciated.
Unfortunately I’m still seeing the persistent notification bug on our installation. Happy to try and help debug.
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?
Did you successfully log into Pavilion and file a bug report about the persistent notification bug? If not, I can do it as I have credentials for the Pavilion site.
Thanks for the reminder! I tried again and was able to create an account and file the report.
FWIW our persistent notification cleared, maybe due to a normal Discourse update and restart. We’re not really using chat heavily though, so it may just be lurking waiting to reappear.
The persistent chat notf issue has been filed and addressed
Please give me any further updates about it in that topic. Thanks guys.
Thanks, I can repro with google auth when going directly to a wizard without an account. I’ve made a bug report for this and will address tomorrow or wednesday.
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
Hi thank for this wonderful plugin. I just notice some thing about this.
If send a message the web push appear. If the user click on that notification it will open the uncategorized chat topic. Same thing if mention user. Is that a feature or bug?
Sometimes the chat it sticking and cannot scroll. I think it mostly happening when someone writing and avatar shows.
Is that possible to disable the page scroll when chat scroll active specially on mobile?
Great plugin, could be a game changer.
- Make the chat window visible to unregistered users
- Push new chat comments to the top of the window, so you don’t have to scroll to the bottom
Those seeing errors with responsiveness and longer messages not being sent are likely hitting API rate limits.
@angus comparing with posting/replying to a message,
typing requests aren’t emitted at all or very seldom there. Could it be that they need to be throttled?
Also any idea which rate limits is this hitting?
Anton, did you give Angus this information in a Pavilion bug report?
He’s previously told us his ability to troubleshoot and fix goes up drastically if you funnel information through the Pavilion bug report process.
For what it’s worth, I’m also experiences issues with responsiveness and longer messages not being sent. Although I don’t have the kind of hard data that you do to back up what I’m seeing.
Thanks, I did now: Hitting rate limit on typing long messages - Bug Reports - Pavilion
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/topic.rb:470:in `for_digest' /var/www/discourse/plugins/babble/app/models/topic.rb:4:in `for_digest' /var/www/discourse/app/models/post.rb:99:in `block in <class:Post>' activerecord-22.214.171.124/lib/active_record/relation.rb:412:in `instance_exec' activerecord-126.96.36.199/lib/active_record/relation.rb:412:in `block in _exec_scope' activerecord-188.8.131.52/lib/active_record/relation.rb:784:in `_scoping' activerecord-184.108.40.206/lib/active_record/relation.rb:412:in `_exec_scope' activerecord-220.127.116.11/lib/active_record/scoping/named.rb:192:in `block in scope' activerecord-18.104.22.168/lib/active_record/relation/delegation.rb:66:in `block in for_mailing_list' activerecord-22.214.171.124/lib/active_record/relation.rb:407:in `block in scoping' activerecord-126.96.36.199/lib/active_record/relation.rb:784:in `_scoping' activerecord-188.8.131.52/lib/active_record/relation.rb:407:in `scoping' activerecord-184.108.40.206/lib/active_record/relation/delegation.rb:66:in `for_mailing_list' /var/www/discourse/plugins/discourse-506investor-digest-plugin/plugin.rb:89:in `get_favorite_posts' /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/lib/distributed_mutex.rb:29:in `synchronize' /var/www/discourse/lib/distributed_mutex.rb:29:in `synchronize' /var/www/discourse/lib/distributed_mutex.rb:14:in `synchronize' /var/www/discourse/plugins/discourse-506investor-digest-plugin/plugin.rb:12:in `execute' /var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform' rails_multisite-2.5.0/lib/rails_multisite/connection_management.rb:76:in `with_connection' /var/www/discourse/app/jobs/base.rb:221:in `block in perform' /var/www/discourse/app/jobs/base.rb:217:in `each' /var/www/discourse/app/jobs/base.rb:217:in `perform' /var/www/discourse/app/jobs/base.rb:279:in `perform' mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:93:in `process_queue' mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:37:in `block (2 levels) in initialize'
I’m experiencing the same issue here. Is the GitHub repository the right place to report this issue?
Hey guys, given the most recent breaking changes, and a few other related technical challenges posed for Babble in the current version of the Discourse codebase, unfortunately I’ve decided it’s not feasible to continue support babble at this stage. So this is being moved to #plugin:broken-plugin.
Believe me, I wish it were otherwise, and was hoping as such until the last few months of core Discourse changes which will require significant changes to Babble to get it working again. I’ve been actively looking for a more dedicated maintainer of the plugin, however there are two issues there. Chat is a difficult use case, and Babble is a complicated plugin. It requires an in-depth knowledge of Discourse itself, as well as Rails and Ember, and dedicated blocks of time to keep up with the changes in Discourse.
I would recommend you consider using a seperate dedicated chat instance alongside Discourse for your community. If you have any questions about setting that up or what to use, I’d be happy to give you some advice on that (for free). At Pavilion we use Mattermost alongside Discourse, which works well for us.
Thanks for all of the work you’ve put into it! Perhaps someone will eventually find a way to pin an external public chat channel from one of these services (mattermost, rocketchat, matrix) into their Discourse for a sort of “live chat”.
We are actively working on an official chat solution. The timeline is still fluid but I imagine we should have something to show in the next couple of months.