Jump to content
Chosen

New content notifications

No Response 2.8.4

After switching from my hosted babble to the chat service I have noticed that the site content notifications don't work the same way.  The posts used to appear in real time when something was added to the site.  Now with the service they only appear if a user leaves chat and goes back in. 

Is this a bug, an intentional thing, or something that I set up incorrectly?

Share this comment


Link to comment

I have tried to use the notification bot and it isn't posting anything in the chat.  I have it enabled and have synced it to the rooms.

Share this comment


Link to comment

make sure:

allow_url_fopen

and

allow_url_include

are enabled for your php. the library that i use for websock for php uses both of these to establish the connection and to send messages.

Share this comment


Link to comment

I posted the follow up with the wrong app.  I am using the service.  Not sure if that matters or now.

Here's a little more information.  The notifications are showing up fine if someone posts in one of the club forums.  But I have posted in every regular forum and haven't received a notification for any of them.  I have selected "All" forums.

Share this comment


Link to comment
3 hours ago, Chosen said:

I posted the follow up with the wrong app.  I am using the service.  Not sure if that matters or now.

Here's a little more information.  The notifications are showing up fine if someone posts in one of the club forums.  But I have posted in every regular forum and haven't received a notification for any of them.  I have selected "All" forums.

regardless of using the service or self host, they both use the same library when using certain bots (time/registration/notifications) all use this library to post to a socket connection, so both of those php functions need to be enabled. i am looking at possible alternatives, but creating a websocket connection with php isn't something in high demand, so the libraries are limited and so is the information on how to do it properly, it is why i have opted to stick with this library even tho it has limitations. 

there is a bug that i came across that i've fixed for 2.8.5, that might be the root cause of this (babble's Member class getting confused on which room the currently logged in member is in) for task, the user would be guest, so i made it where you could also pass a member and what room they are in, but the code was a bit bugged and it was just going with the "default" room, which is the "first" room that is available to the user. 

I'll test to see if i can reproduce the issue. 

Share this comment


Link to comment

Okay i setup a few rooms, assigned the same notification bot to different rooms and it appears to be working.

Somethings to check if 2.8.5 doesn't fix the issue (you can also check with 2.8.4 these too, but i think it was caused by a bug i fixed in 2.8.5):

  • notification bot is run from a task, make sure your task are running (and/or the cron is setup properly,  in the older versions, it would generate and send as the post was being made, but this could take up to 30 seconds and was causing some people issues, so there is now a queue it runs from. this task is set to run every minute, so  you wont see them instantly).
  • make sure the task for the bots isn't locked.
  • in the bots configuration, if you don't have "store" checked, it will only show to you if you are in the room at the time it is sent, if it is unchecked, the notification is a phantom and doesn't get stored to the database. 
  • notifications bot runs from the "read" permission of the app/node it operates from. and it walks backwards. if you can see the forum while logged into the account and read its content you should be able to see the bots notification.
  • run the command /notifications, you might've disabled them at one time, other wise babble will generate the bot message, but it wont show it to anyone who has disabled it via the command. 
  • make sure you don't have the bot member making the post on your "ignore" list, just type in /unignore <bot user name> to see if it tells you they've be un-ignored or if you are ignoring the member. (it be best to create a special members groups for the bot member, and mark that group from being able to be ignored.)

Share this comment


Link to comment
×
×
  • Create New...