A user in our forum reported the below feedback to me, and I agreed that this is really ugly and hurt user experience:
I just viewed a topic without being logged in and I saw a post I deleted still showing up, with the body "This post is deleted!". I think that's rather ugly and that deleted posts should only be visible to the author and admins.
@julian said in Possible bug? Deleted Posts listed:
if the user happens to not be able to see some of them, then a page with 20 topics suddenly only has 18
Does this apply to infinite scrolling as well?
@meshmellow After waited for few hours and I went back to edit the post, it succeeded. Seems like there's some throttling involved.
I got the following error when trying to edit my post here:
May I know why it was flagged as spam by Akismet?
NodeBB allows you to sort posts by votes in a topic, but within a category you can't sort topics by votes.
This plugin allows you to sort topics by votes within a category. See screenshot below, you get a little "Most votes" selection from the "Sort by" dropdown menu.
As requested here and here. Developed and maintained by @xidui and @wktang.
Install it from NodeBB Admin Panel, or
npm install nodebb-plugin-category-sort-by-votes
Go to the ACP (Admin Control Panel).
Activate plugin and reload NodeBB.
Click Plugins -> Category Sort to go to the Plugin's settings.
Click "Re Index" to index all topics (see below screenshot).
Go to any category, select "Most votes" from the "Sort by" dropdown and it should work!
Feature of sorting by votes use cid:[cid]:tids:votes as key, while it is not supported by NodeBB. So we must recreate the index to make it work.
If "reindex" is not applied before you use "Sort By Votes" option in the category page, the category page will be blank.
We also use action:post.downvote, action:post.unvote, action:post.upvote hook to listen user actions and dynamically update the sortedSet which use cid:[cid]:tids:votes as key.
@pichalite Yes. I have tested that if the user is not currently online, the user is able to receive email from executing the above code.
I want to send a chat message to a user, and to ensure that the user will be notified via email, I set the user's lastonline to 5 minutes before current timestamp.
I see that the user's lastonline field is being set correctly (verified via api call), but the user is still not being notified via email.
// set lastonline field to 5 minutes before current timestamp
Users.setUserField(req.params.uid, 'lastonline', Date.now() - 300000, function(err) {
Messaging.newRoom(req.user.uid, [req.params.uid], function(err, roomId) {
Messaging.addMessage(req.user.uid, roomId, req.body.message, timestamp, function(err, message) {
// this should send an email notification to the user
Messaging.notifyUsersInRoom(req.user.uid, roomId, message);
return errorHandler.handle(err, res, message);
});
});
});
This is the condition which determines whether the user is online:
https://github.com/NodeBB/NodeBB/blob/dcb73f9647bd73acce0d0907d04d060e7fe05eb7/src/user.js#L152
I print the lastonline field value inside the isOnline method, which prints the previous set value and this is strange. Is this due to some kind of caching in the db layer? I am using mongodb by the way.
This commit shows that to make the user offline, all that's needed is to set the lastonline field, so I am not sure what I'm missing.
https://github.com/NodeBB/NodeBB/commit/18e68346e713fce2efb49aff0b18bd2bbf0be332
