Jump to content

Michael

Administrators
  • Content Count

    2,764
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by Michael

  1. Michael

    RE: Freezing and resets

    i run babble on a few personal sites of mine, with groups of moderators who monitor it, so it does get test outside of basic use. on average they have about 20 to 30 members at any given time chatting. I have not seen this issue and when i asked the moderators and members on my other sites, they mentioned the issues that were 2.8.4, but they didn't seem to run into this one specifically. keep me up to date, as i am curious what is causing it, cause it seems like the giving into demands to put the editor in has been a bad mistake.
  2. Michael

    RE: Freezing and resets

    Changed Status from Pending to Can't Reproduce Changed Fixed In to 2.8.5
  3. Changed Status from Pending to Closed Changed Fixed In to 2.8.5
  4. okay i sent you a PM here, let me know if it works
  5. never mind, i found you
  6. did you buy form the IPS market? if so, what is your name over there so i can check the key out.
  7. Michael

    User Reported Issues

    nothing in the controller is jumping out at me that could be causing this issue and i can't seem to duplicate it. if you could maybe capture me what the browser console is reporting the next time it happens. it sounds like a disconnect is happening, but the disconnect screen isn't showing up.
  8. Michael

    User Reported Issues

    might be some legacy code from 2.7 that is interfering that i missed or didn't update. the babble controller is like 1600 lines of code
  9. Michael

    User Reported Issues

    I have a 8 core/16 thread desktop and a 6 core/12 thread laptop. i pulled out my old lenovo laptop which is a dual core and noticed this similar issue, but after about 30 seconds it cleared up and started working. I've added some callbacks to the javascript in 2.8.5 so hopefully it lessens cpu intensity a bit.
  10. Michael

    Some Issues Noted

    could you send me the them (send it in PM) so i can take a look at it, and see what is happening.
  11. Michael

    User Reported Issues

    Changed Status from Pending to Can't Reproduce Changed Fixed In to Next Version
  12. Michael

    User Reported Issues

    i believe this has to do with the "return" from idle function, as i tried for awhile today to try to reproduce either one of these and not able to, but i had notice some funky issues when returning from idle. i've got a lot of little tiny fixes coming in 2.8.5 are these ipad users? making websocket connect can be a bit cpu intensive, with older ipads/iphones it appears to "lock up" and/or "freeze" but it can take a bit (i've noticed on my ipad mini 2, it can take up to 30 seconds). I'd imagine the same thing can happen on slower/older android tablets/phones as well.
  13. Michael

    New Room Problem

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  14. Michael

    babble ipad mini

    they can change it their own settings by click on the 3 cogs button at the top of the room, user settings are global, so it will persist thru rooms and devices.
  15. Michael

    babble ipad mini

    it seems there was a bug when it was creating the user for babble_member, it wasn't also saving the default settings (where it sets the acp permission for new users). I've fixed it, so till the change the settings, the acp setting will apply to them by default.
  16. Michael

    babble ipad mini

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  17. Michael

    New content notifications

    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.)
  18. Michael

    New content notifications

    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.
  19. Michael

    New content notifications

    Changed Status from Closed to Pending
  20. Michael

    Command Issue

    Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
  21. Michael

    Sound issue

    stupid pluralization originally i had it listed as just "babble_sound_whisper", when i added in the uploads i change the settings names and i changed it to 'babble_sounds_whispers" but missed 1 place in the JS where it checked to see which sound it should be sending, it was looking for 'babble_sound_whisper'. this has been corrected in the next version.
  22. Michael

    Sound issue

    Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
  23. Michael

    Sound issue

    Changed Status from Pending to Work in Progress
  24. Michael

    Command Issue

    Changed Status from Pending to Work in Progress
  25. Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
×
×
  • Create New...