.category-children-item {
  display: flex;
  float: none !important;
}

seems to do the trick.

EDIT:
after looking a bit at the topic @crazycells linked and looking at this for a few more minutes I think the better solution would be:

.categories .category-children {
  display: flex;
  flex-direction: column;
}

It doesn't affect how it works, but not using !important is the improvement here

Oh, and if you want some distance between the items just add margin-top or margin-bottom to .categories .category-children-item.

It is possible, but you need nodebb-plugin-markdown 8.11.1 or higher, while package.json has the exact version of this plugin selected, so unless you installed your NodeBB recently, you have to either upgrade NodeBB if you're on master branch (git fetch;git reset --hard origin/master;./nodebb upgrade), switch to master branch, wait for next minor 1.13 version or install it manually via npm install nodebb-plugin-markdown@latest - with the last option being the easiest.

In that version a plugin for markdown-it was added that adds parts of multimarkdown syntax - specifically, better table syntax. You will be able to create multiline tables like this:

| header1 | header2 | header3 | header4 |\
| units   | units   | units   | units   |
|:-------:|:-------:|:-------:|:-------:|
| data1   | data2   | data3   | data4   | 

When you add \ at the end of a row markdown parser will now interpret it as a multiline row and merge it with the one below. So this example table will look like this:

There is more to this syntax than just merging two rows (for example single cells spanning multiple rows or columns) and you can find the documentation of this plugin here

v3 is not just "a better reCAPTCHA" and it is not replacing v2.

v3 only offers "invisible" reCAPTCHA, but even if Spam Be Gone supported that (it doesn't yet) it still wouldn't work because it passes different data.
reCAPTCHA v2 is binary - either user is a robot or not.
v3 doesn't just pass "true||false" but instead passes a score from 0.0 to 1.0 and it's up to the application to determine what score is a success. It also never shows user a challenge as it's not supposed to interrupt the user in any way.

So to sum it up: for Spam Be Gone to support v3 would mean changing the way it handles reCAPTCHA and I'm not even sure if it's a good idea. v3 is supposed to continuously chceck if user is a bot without interruptions, so it's best used for frequent user actions like posting or login, not for things like registration that happen once per user and it's not a big deal if it interrupts user with a challenge. So I'd say it'd be better for Spam Be Gone to extend its functionally to use v3 on login and posting, and leave v2 on the registration page.

It's already been added some time ago and will be in 1.13.0:
https://github.com/NodeBB/NodeBB/commit/1796b65d34e5762e95e1bd305d3bc90983059811
The original issue on GitHub:
https://github.com/NodeBB/NodeBB/issues/7770

alfazaz created this issue in NodeBB/NodeBB

closed Disable user to quit a group (permission) #7770

0 julianlam committed to NodeBB/NodeBB

feat: option to restrict group leaving, closes #7770

If you want two columns try this:

.categories .category-children {
  display: flex;
  flex-wrap: wrap;
  flex-direction: row;
}
.categories .category-children-item {
  flex: 1 1 45%;
  margin-top: 1vh;
}

You can increase the number of columns by changing that 45% to some lower number (it actually can be a little higher, but it seemed to go to 1 column on above 48% for me. 45% was just more "round" number close by
That margin-top is there because otherwise the items were touching at the top and bottom and it didn't look good for me

The only problem here is with longer subcategories - especially with mobile devices. I think if I wanted to do something like this I would try to change it to just one column if the screen width is too small.

The only current milestone on GitHub is 1.13.0, so I'd assume that it will wait for that release.

If you need it now you can manually modify some NodeBB files:

• in src/middleware/user.js modify line 135 from

					user.isModeratorOfAnyCategory(req.uid, next);

to

					user.isAdminOrGlobalMod(req.uid, next);

• In src/socket.io/posts/tools.js change line 75 from

				if (!results.isAdmin && !results.isGlobalMod && !results.isModerator) {

to

				if (!results.isAdmin && !results.isGlobalMod) {

• in src/controllers/accounts/helpers.js change line 144 from

			if (isAdmin || isSelf || ((isGlobalModerator || isModerator) && !results.isTargetAdmin)) {

to

			if (isAdmin || isSelf || (isGlobalModerator && !results.isTargetAdmin)) {

That should remove all privileges from category moderators while leaving them for administrators and global moderators.

I'm really looking forward to 1.13.0 though, as I've not only added two things that will be useful for me (not to mention useful changes by NodeBB staff and other contributors. And the refactor), but also because I use the master branch for my dev enviroment the plugin I'm currently writing uses async/await where 1.12.x doesn't support it yet, so to avoid rewriting it twice I had to use util.promisify to make current callback based functions work like async ones

EDIT: btw. It seems like 1.13.0 might be close as there are no issues left assigned to this milestone. So while I'm not NodeBB staff and can't tell you when the refactor will be finished and when they think there are enough changes for an update to 1.13 I doubt it's really far away

@crazycells
Responding from a phone, so I can't make a full solution right now, but I think the best way would be to select it from correct <li> element using cid. Like this:

.categories li[data-cid=x] .category-children {
...
}
.categories li[data-cid=x] .category-children-item {
...
}

Where x should be replaced with the cid of the category you want to style.

I didn't check this, but it should work

You could also use :nth-child, but I think that's worse because reordering categories or adding subcategories to one that didn't have them might break it.

There is a global chat plugin: https://github.com/NodeBB/nodebb-plugin-global-chat

And actually I'm not entirely sure, but I think cookies that are needed for the service to work (like session cookie that would cause some problems when disabled by an anonymous user and make logging in impossible) don't actually need to be opt-in.
Still - it would be nice to have a uniform cookie opt-in banner that could be expanded in plugins. Even if you couldn't opt-out of session cookie due to the way NodeBB works. Because plugins that add analytics, or even some social media buttons might need that kind of a banner.

Admin>Manage>Privileges
Just select a category you want to apply this restriction to (if you want it to work globally, you can select any category and just copy its settings to all) and remove "create topics" privilege from everyone but Global Moderators.

There actually were some WebRTC based plugins before NodeBB 1.0, but I don't think there are any working ones now.
Adding it would require creating a new plugin, so it would certainly be complicated. However, it's definitely not impossible and it's probably not that hard nowadays, because you don't actually need to handle anything with voice or video - as others had done that before probably better that you would. If you or someone from your forum would actually want to try creating such plugin, integrating Jitsi Meet might be one of the best ways to do it.
Jitsi is open source, has an API for integrating it into other webapps and also allows for self-hosting (which not only means better control over the installation and data, but also the number of users will be limited only by how powerful your server is instead of being capped at 75 like on meet.jit.si). And since it's a videoconferencing platform it will also have features connected with that like screen sharing or recording the meeting.

I think it stopped working in 1.13 - I remember it being there in 1.12 and there were no updates to that plugin for a long time.

I'm not sure if it wasn't a little bugged though - if I remember correctly the side effect of disabling notifications was that your chat window stopped updating global chat at all. You had to reload the tab (or possibly just reopen the popup window if that's what you used) to get new messages.

It is possible, but you need nodebb-plugin-markdown 8.11.1 or higher, while package.json has the exact version of this plugin selected, so unless you installed your NodeBB recently, you have to either upgrade NodeBB if you're on master branch (git fetch;git reset --hard origin/master;./nodebb upgrade), switch to master branch, wait for next minor 1.13 version or install it manually via npm install nodebb-plugin-markdown@latest - with the last option being the easiest.

In that version a plugin for markdown-it was added that adds parts of multimarkdown syntax - specifically, better table syntax. You will be able to create multiline tables like this:

| header1 | header2 | header3 | header4 |\
| units   | units   | units   | units   |
|:-------:|:-------:|:-------:|:-------:|
| data1   | data2   | data3   | data4   | 

When you add \ at the end of a row markdown parser will now interpret it as a multiline row and merge it with the one below. So this example table will look like this:

There is more to this syntax than just merging two rows (for example single cells spanning multiple rows or columns) and you can find the documentation of this plugin here

What I learned from this post:

1. The bubbles at the bottom were supposed to be a task bar and plugins could integrate into it. Never seen anything other than composer and chat do that, so I didn't even consider that being a possibility...
2. There was some "settings v3".

That is to say, while I went into it thinking "I wonder if they will cut out something useful", but it turns out that it really is just cleaning up some rarely used or hard to maintain, even if kinda cool at least conceptually, functionality. So I have high hopes for lack of feature creep in 2.0

I'm not really sure what you're trying to do here - if you want to copy a repository to a local folder you should use git clone and not git checkout - the latter is used for switching branches and generally moving to a different version of a repository.
However, got should not be used to install a plugin. NPM is the utility you're looking for. It supports two methods of authentication for GitHub private repositories - OAuth and SSH.

For OAuth you'll need to generate a personal access token (settings>developer settings>personal access tokens) with permission to read private repositories (just repository permissions if I remember correctly), and then go to the main NodeBB directory and use npm install git+https://<github_token>:x-oauth-basic@github.com/NodeBB/nodebb-plugin-xxx.git

If you prefer to use SSH instead, follow the instructions here to generate the keys and add to your account, and then run in the main NodeBB folder npm install git+ssh://git@github.com/NodeBB/nodebb-plugin-xxx.git

the "host" part in MongoDB config is there for a reason

And no, NodeBB Docker image doesn't contain any database. You can see the dockerfile here - notice there is no mention of neither MongoDB, redis nor PostgreSQL. The choice of DB is left to you.

I don't think Docker should interfere with remote connections, so just changing mongodb/redis/PostgreSQL uri should work.

However, I'm not don't think that NodeBB can run serverless. It runs it own web server and uses websockets - so with Zeit small time limits even if you got NodeBB to run, the client would be reestablishing websocket connection every 10 seconds.

Going serverless seems great for apps that only need server-side processing occasionally. If you only can divide the app into small tasks that need to be done from time to time - for example every time the user requests a webpage.

Adapting NodeBB to work with Zeit Now, AWS Lambda, Google App Engine, Azure Functions or whichever serverless platform you want to use would require a lot of work. Socket.io would have to be replaced with something that supports serverless apps until a way to use it that way is added (I believe Zeit is working on this, but they are at it for some time now. And a lot of things would have to be moved away from NodeBB app itself to the selected serverless platform.

But I'm not really experienced with neither serverless nor docker, so I might've misunderstood something.

Created an issue and a PR with working markdown-it-multimd-table now

The syntax really isn't too esoteric in my opinion:

1. multiline - just add a slash at the end of a row and it will be merged with the next row.
   So the table from the first post would look like this:

| Fruit           | Price             | Advantages |
| :--------------  | :------------------ | :------------------- |
| Bananana | first line       | first line        | \
|                    | second line | second line |
| Bananana | first line        | first line       | \
|                    | second line | second line |

2. if you want a cell to span multiple columns just end it with the amount of pipes equal to number of columns you want it to span. Essentially - create a totally empty cells without even a space inside.
   For example:

| 2-column header                     ||
| :--------------------- | ----------------------:|
| single column| single column |
| two columns                             ||

3. Rowspan is done by including ^^ in the cell below the one we want to span multiple rows. So for example:

| Fruit           | Price             | Advantages |
| :--------------  | :------------------ | :------------------- |
| Bananana | two rows      | one row        | 
| Bananana | ^^                   | one row        |

4. headerless is self-explaining I think Just don't add any header and do everything the same way as it was done.

Just so it isn't missed in an edit: I found a markdown-it plugin that would fix this
https://github.com/RedBug312/markdown-it-multimd-table
It expands markdown table syntax greatly, allowing cells to span multiple columns and rows, create multiline cells without html, and create headerless tables. It seems to be based on MultiMarkdown syntax for tables, so at least there is also some standard.

There actually might be a way to support it without changing markdown-it code (which won't happen, see here: https://github.com/markdown-it/markdown-it ) and without even creating a plugin for it.
In available options there is a setting breaks that is disabled by default, but when enabled should convert \n inside paragraphs into <br> while parsing, which would enable users to insert <br> into tables without working html...

Oh, that's weird. It's actually enabled in NodeBB always - there is no setting to turn it off. Yet \n doesn't work as seen here. I think I'll create an issue in nodebb-plugin-markdown and investigate it, cause I don't think that's expected behavior? Is it sanitized at some point and turned back into \n, changed before markdown-it parses it, or what?

Edit: ah, nevermind. I misunderstood this option. It's why a single newline works as a line break here, and it's not about turning \n as written into a <br>... \n is just \n to markdown-it...

By default you can't do it. You'd need to either:

1. create a plugin to add that functionality
2. use alternative sanitization (install nodebb-plugin-sanitizehtml and disable html sanitization in markdown plugin).

The second way is much easier, but due to the html parser used it has its own problems (for example if you ever want to write that something is less than or equal something, you can't use x<=y, because it will think you started a html tag and will cut out your post until > is found or until the end. It's not really fixable unless sanitize-html changes its parser to something like parse5... It can only be worked around manually by modifying the plugin).

Markdown doesn't have a line break tag other than actual line ending, so because it's basing the parsing on line endings you can't have more than 1 line in a cell.

EDIT: Markdown actually has a line break - but since NodeBB treats soft line breaks as new lines and not spaces, it's not really useful here usually. However, ending a line with a \ and a single enter (or 2+ spaces, but a backslash is more visual) will create a hard line break.
Perhaps making it work without disrupting a table cell would actually be a good idea? It'll make them harder to write, as you'll have to do something like:

| first line of fists cell\
second line of first cell | first line of second cell\
second line of second cell | first line of third cell |

But it's much better than nothing.