@scottalanmiller is correct, those numbers are produced on the fly based on active websocket sessions, and not stored anywhere. However, you might be interested in https://github.com/barisusakli/nodebb-plugin-browsing-users, which brings a live-list of current users in-topic back to topic.tpl

@bentael said in away, busy invisible etc. UserStates: away - when user is online but no activity for an X amount of time. busy - set by user invisible - set by user etc. Currently, it seems that the 'away' state is not auto-enabled when user has no activity for a certain amount of time : If it is really the case, wouldn't be greater like this ? (in fact, I need this functionality but don't see it working... Found no code about this in nodebb source code). If it is not the case, what is the time amount for status change to 'away' ? Can it be changed ? @administrators : Add on... Would it be possible to have the following operating mode for statuses (more realtime, with socket.io, like smart messaging apps) ? When a user is previously logged in nodebb : If he makes actions on nodebb (open a page, posting, typing, scrolling...) and if he is not in 'dnd' or 'invisible' or already 'online' mode, auto-set him in 'online' status and update status on all connected clients (update widgets etc...). If he doesn't do anything for a while and if he is not in 'dnd' or 'invisible' or already 'away' mode, auto-set him in 'away' status and update status on all connected clients. If socket connexion is lost, auto-set him in 'offline' status and update status on all connected clients. If socket connexion is reconnected, auto-set him in its previous status and update it on all connected clients. etc... In short, knowing in a more realtime status of the users would be a big plus for nodebb. I know it can be ressources consuming but there may be a trick with socket.io (?). Another thing : online-cutoff time seems too restrictive for me. If a user is inactive more than this time, he should go into 'away' state but he could always receive notifications because he is not offline. There could be a different time to cut notifications... (sorry for this long post ! Hope I'm clear ; I'm french... )

Hi all, We are going to be using NodeBB for our company user group. My supervisor has asked if during the user registration if we can ask for a couple of more fields. Specifically we want to know either the company or institution the user is with and also an instrument serial number. What would be the process to get these added to our user database? Thanks!

@Esha Install plugin. Activate plugin. Rebuild and restart. Go to Admin -> Customize -> Widgets (or search widgets in the admin search)

@nhl-pl good

@julian :rage2:

Sorry for bothering guys, I found it in the source code. There are two hooks already: action:group.join action:group.leave Both of them takes only one argument: { groupName: groupName, uid: uid } join: https://github.com/NodeBB/NodeBB/blob/master/src/groups.js#L633-L675 leave: https://github.com/NodeBB/NodeBB/blob/master/src/groups.js#L711-L742 Exactly what I'm looking for! Edit: action:groups.* hooks in the source code were renamed to action:group.*

I am working on a very specific project at the moment and am curious as to whether it would be possible to just manage users and permissions via a MySQL database, and nothing else. Chime in if this is a possibility and what road I would take to achieve this.

I sure did, let me tell you! 6K users!!

So is there a reliable way to set all current members as account confirmed, so they don't have to confirm their accounts, but all new members do?

@gaasg No problem, you can click their name in users of the ACP and it takes you to the same place, do bear in mind that they can change their name back if they wish to.

Yeah, some blind fixing for gh#1741 caused this to happen, but to be honest, that bug was kind of hard to reproduce, so that side effect cropped in No clue how to handle the existing users with "undefined" as their username... hm Xandaros created this issue in NodeBB/NodeBB closed Calling user.create with existing username #1741