@oplik0 said in snowing theme:

<script src="https://cdn.jsdelivr.net/gh/nextapps-de/snowflake@master/snowflake.min.js"></script>

try it in combination with nodebb-plugin-night-mode!  it becomes a heartwarming winter dream.

hi.

i'm pretty new to nodeBB - it's my first thread/post.  we are a group of seven enthusiasts who moved a nearly 20 year old voluntary sports-forum in germany from a proprietary internet forum software to nodeBB.  first of all: we are really happy with our choice =;^)  it's a great piece of software!

but there are some wishes.  of course.  after some investigation on the topic "counts for /flags and /post-queue" i felt asking here should be the best option.

we are using the /post-queue as a part of our spam-protection strategy.  our /post-queue is in the navigation visible to moderators and admins.  it would be great to have the count of posts inside as a marker on it like for /unread.  the same for /flags.  we would love to see the open issues marked there.

well.  if you have any advice because we missed something obvious feel free to help.  thank you.

ober!schöne grüße,
mrx.

@julian said in counts for /flags and /post-queue:

@murcs As the changes were contained in multiple commits, it may be easiest for you to wait for v1.16.2 (this Wednesday)

oh!  great.  just three days to wait.  sounds fairly okay =;^)

@baris thank you for all the details.  i'll try to "fix" it by myself.

hi.

i'm still pretty new to nodeBB - it's my second thread.  we are a group of seven enthusiasts who moved a nearly 20 year old voluntary sports-forum in germany from a proprietary internet forum software to nodeBB.  ... and we are still happy with our choice =;^)  it's a great piece of software!

we are using the nodebb-widget-board-stats widget in a self-localized and customized version.  we found a distinct discrepancy of the active users count shown by the widget compared to the dashboard.  as far as i understand the active users count is calculated by

105        db.sortedSetCount('users:online', now - 300000, '+inf', next);

of library.js while the guest count is required by

108        require.main.require('./src/socket.io/admin/rooms').getTotalGuestCount(function (err, guestCount) { ...

as a live-value from nodeBB.  unfortunately i have no idea where the active users count shown in the dashboard comes from.  it's definitely not calculated the same way!

we had to treble the span of time from 300000 to 900000 like in

105        db.sortedSetCount('users:online', now - 900000, '+inf', next);

to come closer to the active users count shown in the dashboard but it depends on some undisclosed criteria - user activities or devices or whatever - that both values still differ significantly in both directions.  my questions are:

1. how is the active users count shown in the dashboard required?
2. how to get the same value for the nodebb-widget-board-stats plugin?

some other thoughts: i'm wondering why the span of time is hard coded in the widget.  from a more user perspective i would expect the "onlineCutoff" found in the "config" key is taken into account.  in both places!

... and i have an additional "{count24h} users were active for the last 24 hours." on my personal wishlist, based on something like

...        db.sortedSetCount('users:online', now - 8640000, '+inf', next);

i will try to achieve this by myself.

ober!schöne grüße,
mrx.

dear @julian.

i'm not aware, if it's possible to kind of patch those lines to our v1.16.1 nodebb instance.  ... or do we have to wait for v1.17.0 which could take some months?  if it's not too difficult give me a short advice please.

ober!schöne grüße,
mrx.

@baris said in All users' status is invisible:

The script @pitaj posted will set lastonline field of the user to Date.now if you don't want that remove it from the data object above.

unfortunately we had to remove the other lastonline line(s) in setUsersOnline()too.

function setUsersOnline(callback) {
	var batch = require('./src/batch');
	batch.processSortedSet('users:joindate', function (uids, next) {
//		const lastonline = Date.now();
		const data = {
//			lastonline,
			status: 'online',
		};
		async.parallel([
			cb => async.each(uids, (uid, next) => {
				db.setObject(`user:${uid}`, data, next);
			}, cb),
//			cb => db.sortedSetAdd('users:online', uids.map(() => lastonline), uids, cb),
		], next);
	}, callback);
}

no idea why lastonline is manipulated by the script anyway.  to force a re-login to see it taking effect the forum was rebuild and restarted after running the script.

@julian said in counts for /flags and /post-queue:

Let me look into it for you and see...

great.  let's hope it's perfectly documented.

ober!schöne grüße,
mrx.

well.  2 votes are nice but after a week something official inbetween "good idea.  wait for version 1.33.something!  minimum." and "doesn't make sense for us.  write your own plugin, if you really want it!" would be great.  thank you.

ober!schöne grüße,
mrx.

@baris thank you for the detailed explanation.  i was afraid setting lastonline to Date.now() is needed to manipulate the status field in the database.

we have already seen that users are automatically set to offline after some [30?] minutes of inactivity - this is absolutely wanted as long as the status field in the database stays untouched.  great!

@baris said in All users' status is invisible:

@pitaj mentioned where to put the file, it goes into your nodebb installation folder, so in the same folder as your config.json.

you are right.  one should read until the end of a post.  sorry.

A user is set to online when they register and then it is up to the user to change the status. For example a user can set their status to offline if they don't want to be seen online.

i know.  but more than 29,000 migrated users were set to offline (by fault) and didn't choose it.

frankly speaking i would expect the software to set my status to online whenever i log on.  let's say my status was set to absent - for whatever reason i forgot in the meantime - before i logged out.  when i come back later i'm not absent anymore - i'm online.  in my opinion it should be no choice - for a normal user at least - to stay invisible forever.

the other question was if the value of lastonline will be changed by the script to Date.now() or not?  i would prefer to leave it unchanged.

sorry for pulling this topic up.  but we face the same problem: after migrating from a proprietary forum software four out of five users logged on are set to "offline" while they are obviously online and active.  the "online" users are either new or changed their status manually.

the title should be "all migrated users' status is invisible"

on the one hand i have basically no idea where to run the script mentioned by @PitaJ.  on the other i'm not sure if the value of lastonline will be written to Date.now() then which would be nice to leave unchanged.

i'm wondering why a user isn't set to "online" by default with every login and has to change the status every time to "offline" or whatever manually if needed?!