Let's keep a list of NodeBB installations here :

If you are running your own NodeBB let us know we will add it to the list!

Just merged the group-chat branch into master, it will be available in our next release which will most likely be 1.0.0.

There are some breaking changes and schema changes in this merge.

The upgrade script will go through all the chat messages and assign them to rooms. This might take a while depending on how many chats messages there are in the system. The upgrade script should show the progress in the console.

For all the changes check out this PR https://github.com/NodeBB/NodeBB/pull/3968/files

barisusakli created this issue in NodeBB/NodeBB

closed Group chat closes #1798 #3968

This NodeBB plugin pulls RSS feeds and creates topics in predefined categories.

https://github.com/barisusakli/nodebb-plugin-rss

To customise options for the parser, please consult the "RSS" page in the administration panel, under the "Plugins" heading.

Installation

npm install nodebb-plugin-rss

Usage

1. Click 'Add Feed'
2. Enter the RSS feed you want to pull
3. Select the category you want to post to
4. Enter tags if you want to tag the posted topics
5. Type in the username you want to post as
6. Select the interval to query the RSS feed
7. Select the timestamp to use for the topic
8. Click Save.

I have run some tests to check the memory usage.

The redis INFO command was reporting 811kb at the beginning since I was running the tests on db1. An empty NodeBB installation starts with roughly 405kb of memory usage.

start 811.44 kb

**Users **
100 users 1.04M diff (254kb) per user = 2.54kb
1000 users 3.61M diff( 2,885kb) per user = 2.885kb
10000 users 29.88M diff( 29,786kb) per user = 2.97kb

Posts (500 chars each)
336 posts 30.71M diff(849kb) per post = 2.52kb
996 posts 32.70M diff(2,887kb) per post = 2.89kb
9995 posts 54.39M diff (25,098kb) per post = 2.51kb

The memory usage per user is roughly 3kbs at 10,000 users. This value goes up as we have other structures that grow as the user count grows.

The memory usage per post is about 2.5kbs per post, keep in mind the posts I created are all 500 characters long.

So for 2,000,000 posts and 400,000 users :

2,000,000 x 2.5kb + 400,000 x 3kb = 5.9gb

So theoretically 6gb should be enough.

Hope that helps.

We recently added a new system group called Global Moderators, this group has access to the moderator tools but can't access the ACP. They can also ban users. We will let this group see banned users and flagged posts as well.

We have assigned some users as global mods on this forum as well https://community.nodebb.org/groups/global-moderators.

If you think we missed someone or you want to be a global mod ask for it here.

NodeBB Plugin Browsing Users

This plugin shows who is currently viewing a topic. This was a core feature that we removed a while ago, now it is back as a plugin

Installation

npm install nodebb-plugin-browsing-users

More info at https://github.com/barisusakli/nodebb-plugin-browsing-users

Notes
Currently only persona supports this, if you want to add it to your custom theme make these changes.

Your best posts

This is just a simple theme based on persona that modifies the topic view with a sidebar.

Here is a screenshot when you are at the top of a topic.

Imgur

And here is one when scrolled down.

Imgur

The sidebar is a bootstrap affix so it is always visible when you scroll down, useful when using infinite scroll as well.

The sidebar also reduces the width of the posts so I find it easier to read compared to long horizontal lines.

Reply, sort by and watch are always visible previously they would go out of screen.

There is a lot more room for browsing user images.

You can install it with npm i nodebb-theme-peace

Just committed https://github.com/NodeBB/NodeBB/commit/7610c11cd1b9de53ce185227ab80f86d55d3bd69, this is a pretty big change even though it's just ~300 lines of code. It changes how we store the main post so that alternative sorting works.

If anyone decides to upgrade please make a backup of your database just incase something goes wrong, I have tested it on this forums dataset and it seemed OK but you never know :). Will do more testing as we get closer to 0.5.0.

There are 3 options to sort oldest to newest, newest to oldest and most votes. The sorting can be changed from a dropdown in the bar below the main post and it is saved as a user setting. The admin can also select a default setting from the ACP.

Let us know if you encouter any bugs.

5 barisusakli committed to NodeBB/NodeBB

closes #450

backup database before upgrade!
upgrade script will take the first post of each topic and set the
`mainPid` property on the topic. then it will remove that pid from the
sorted sets for that topic, this was done to make alternative sorting
work.

added a new sorted set called `tid:<id>:posts:votes` that is used to
sort topic posts by vote count, the original sorted set `tid:<id>:posts`
is used to sort by oldest first or newest first.

the main post is added to the returned posts array on topic load and is
always at the top.
theme changes are minimal just a few new data properties on the posts
and the sorting dropdown.
hopefully didn't miss anything too critical.

Thanks to @Ben-Lubar we now have replies to posts. https://github.com/NodeBB/NodeBB/pull/5050

Right now it only displays one level of replies but you can modify your theme and remove this conditional https://github.com/NodeBB/nodebb-theme-persona/blob/master/templates/partials/topic/post.tpl#L87-Lundefined then you will get nested replies as well.

You can update to master or wait for 1.3.0 to get the feature. It looks like this.

As usual please report any bugs you find on our tracker at github.

BenLubar created this issue in NodeBB/NodeBB

closed Add a sorted set for replies-to-this-post #5050

That message could mean a server crash so check your nodebb logs as well.

Please open an issue on our github tracker.

Does it work if you change bootswatch to "bootswatch": "^3.4.x", in package.json?

Ignore previous commit, this should fix it properly https://github.com/NodeBB/NodeBB/commit/071506eb7dc99e057b5bfde4543eadb75174a19a

0 barisusakli committed to NodeBB/NodeBB

fix: invite properly

Thanks for reporting fixed in https://github.com/NodeBB/NodeBB/commit/8f4b99a41c6496cbdaaf489f16ecbe261d6c4a79

0 barisusakli committed to NodeBB/NodeBB

fix: admins not seeing invite button

It roughly goes like this.

#1 Serialize the form data and send it to the server.

submitBtn.on('click', function () {
  $.ajax(config.relative_path + '/myplugin/saveform', {
        data: $('#form').serializeObject(),
	type: 'POST',
	headers: {
		'x-csrf-token': config.csrf_token,
	},
	success: function (data) {
     	    console.log('success');
	},
        error: function(xhr, status, errorThrown) {
            console.log(arguments);
        }
  });
  return false;
});

#2 Create a post route in your plugin's static:app.load hook, and save the incoming data.

const db = require('./src/database');
plugin.init = async function(data) {
  data.router.post('/myplugin/saveform', [data.middleware.applyCSRF], async function (req, res) {
      await db.setObject('my-plugin-data', JSON.stringify(req.body)); // // req.body has the form data
      res.json('success');
  });
};

If your data is a flat object then you can save it without using JSON.stringify with just db.setObject('my-plugin-data', req.body);

That would be

.topic .content {

}

You need to target the correct element, you can inspect the elements in your browser console to find the correct selectors.

For example

.composer .preview {
font-size: 24px;
color: green;
}

Will change the font-size and color of the composer.

You will need to add it to the topic controller as well. https://github.com/NodeBB/NodeBB/blob/master/src/controllers/topics.js

A better way to do this is to write a plugin and alter topics:read privilege to false if the email is not confirmed.

I added 2 hooks for this in https://github.com/NodeBB/NodeBB/commit/d080c7b04c83a6c2925d8a61f26dc268829afdc2.

Here is how it would be used in a plugin

// this handles multiple users for a single privilege/category
myPlugin.isUsersAllowedTo = async function (hookData) {
	if (meta.config.requireEmailConfirmation && hookData.privilege === 'topics:read') {
		const userData = await user.getUsersFields(hookData.uids, ['email:confirmed']);
		hookData.allowed = userData.map((data, index) => hookData.allowed[index] && data['email:confirmed']);
	}
	return hookData;
};

// this handles single user for multiple privileges or categories
myPlugin.isUserAllowedTo = async function (hookData) {
	if (meta.config.requireEmailConfirmation) {
		const emailConfirmed = await user.getUserField(hookData.uid, 'email:confirmed');
		if (Array.isArray(hookData.privilege) && hookData.privilege.includes('topics:read')) {
			const index = hookData.privilege.indexOf('topics:read');
			hookData.allowed[index] = hookData.allowed[index] && emailConfirmed;
		} else if (Array.isArray(hookData.cid) && hookData.privilege === 'topics:read') {
			hookData.allowed = hookData.cid.map((cid, index) => hookData.allowed[index] && emailConfirmed);
		}
	}
	return hookData;
};

0 barisusakli committed to NodeBB/NodeBB

feat: add 2 hooks for modifying privileges