ArrowChat

When you run the ArrowChat Maintenance, does it suppose to close all opened private chat boxes? It seems like the maintenance cleans up the message but leaves the chat boxes open. This is causing Arrowchat to show up at the bottom in very very delayed. Some of my members have like hundreds of chatbox that have been left opened.

Hundreds?! It's a good thing v4 limits the number of them 🤣 Somewhere around 15-20. Also, the efficiency of loading chat tabs has been greatly increased.

Unfortunately, the maintenance does not clear that setting.

Hundreds?! It's a good thing v4 limits the number of them 🤣 Somewhere around 15-20. Also, the efficiency of loading chat tabs has been greatly increased.

Unfortunately, the maintenance does not clear that setting.

Need help now to many members with chatboxes open & recent chats on mobile.
1. Is it possible the admin (me) to close them via the phpMyAdmin?
2. What file can I (myself) edit to remove Recent Chat now (on mobile)?
3. v4 should have the option to disable Recent Chats just like we have the option now to disable "Enable Online List" .
4. The limit "15-20" should be included in the admin panel that way each admin can decide on the number.

Yeah, unfocus_chat and focus_chat in arrowchat_status need to be set to null.

Good idea! The number that limits the open chat tabs is in a single file so it will be easy to add to the admin panel.

Yeah, unfocus_chat and focus_chat in arrowchat_status need to be set to null.

Good idea! The number that limits the open chat tabs is in a single file so it will be easy to add to the admin panel.

In the PHPAdmin arrowchat_status "structure" both are already set to NULL by default.

You have to clear them all for each user. If you go to "Browse", you'll see that users will have values for that field.

Code: Select all

UPDATE arrowchat_status SET unfocus_chat = NULL, focus_chat = NULL

Thank you! That code works great. I will use it once a week to keep the site running smoothly.

Is this code no longer necessary? Doesn't seem to work with v4.0.2

Is this code no longer necessary? Doesn't seem to work with v4.0.2

Nevermind... code works fine with v4.0.2