.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

.moderator-tools .fa-ellipsis-v:before{
  content: "some text";
}

This will replace these three dots, but if you want to keep them you can also do

.moderator-tools .fa-ellipsis-v:after{
  content: "some text";
}

Note though, that in the second case it will look ugly without any additional styling - I'd recommend adding at least padding-left or margin-left.

You can of course style these pseudoelements in any way you want to. So for example you can create this menu that no one will miss:


by using this css:

.moderator-tools .fa-ellipsis-v:before{
  content: "menu";
  margin-left: -10px;
  color: #FF00FF;
  background-color: #FFFF00;
  font-size: 2rem;
  border-radius: 3px;
  font-weight: bolder;
  text-transform: capitalize;
  font-family: "Comic Sans MS", cursive, sans-serif;
}

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

Markdown works for me. Before 1.13 I needed HTML there tho (this commit changed it). Now it's parsed like a post - so whatever you use for text formatting for users should work.

@rivalite said in nodebb allows users to change the skin and save this appearance?:

3. is there a free spanish translation?

Yes. You can check its status and contribute on NodeBB Transifex project: https://www.transifex.com/nodebb/nodebb/
As of writing this 93.3% of strings in NodeBB are translated to Spanish (and I'd expect that most of the untranslated ones are in ACP, so not visible to users)

5. Is it possible migrate from xenforo 2.x ?

Yes. There is nodebb-plugin-import it requires a bit of work and I'm not sure if there is a Xenforo import specifically (perhaps vBulletin on me might work? If not, perhaps it could be adapted to work - might be easier than making one from scratch, but still would require additional work)

6.I just signup here using an email from https://temp-mail.org/ . Is there a spam filter to don't allow users signup with https://temp-mail.org/ ? This spam filter is free?

https://github.com/NodeBB-Community/nodebb-plugin-email-blacklist - didn't test it with 1.13, but I think it should work considering it was updated 4 moths ago.

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.

You can try creating a PR, but I doubt it will get you anywhere since last commits there were on 2018 and that was a PR too. The creator was last online on this forum in 2017, so I doubt he'll help you here.
Making a fork is probably the best idea here, since it's unlikely you'll get your changes to the main repo.

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

TBH I'd expect that now NodeBB could be considered "notable enough". Especially since there is some forum software that seems to be smaller there:
Thredded has a page an an entry in the comparison article, despite it having less media coverage (looking at news section in google, there is nothing, when there a few articles that at least mention NodeBB), and less stars and forks on GitHub.
There is actually a note that the article may not meet notability guidelines on the thredded page, but apparently it has been there since 2016 and other than one deletion that was contested nothing happened to it. Ironically, one of the links by the person contesting it is to a NodeBB instance
I'd say the same about Syndie, though I can't be sure because I find a lot of articles about a lot of things, but not the forum software. And also - its last release was in 2016...
Beehive Forum has mostly dead links and 2 of 5 external references are just sites that were using Beehive. 3 others are about one vulnerability...

So, I think that unless editors personal feelings would affect their work or they want to wipe a few other pages about forum software (if that's the case, then sorry to these projects!), NodeBB is notable enough by Wikipedia standards by now.
There is even a book mentioning NodeBB now: Node.js Design Patterns (There are actually a few, but this one is relevant and gives some information about NodeBB - not just mentions it).

Though I think the problem of NodeBB and other forum software is that... There is very little news outlets might talk about. Unless there is some big vulnerability or something, it's just usually nothing newsworthy. So there is a lot of things like tutorials for NodeBB, but very little "news coverage".

Oh well, I might give writing a new Wikipedia article a shot, though I'm not very experienced with Wikipedia and I think I might have an oversourcing problem (that is, last time I edited a Wikipedia article I removed half of the sources I added before publishing the changes, because no one needs a source every sentence where one is more than sufficient...)

I now feel really weird because I feel like this discussion is now literally an argument where all sides agree

I don't disagree that the cost of ownership shouldn't apply here. That's what I stated in the original post. If you use it in this context, why not in other contexts? At some point the word "free" just stops existing because everything has some cost attached to it - so nothing can be free.
Or as @Per0x put it:

all those supposedly free presents I got at Christmas were fake

Which is kinda stupid.

@scottalanmiller said in Some questions :

@oplik0 said in Some questions :

I, for one, will agree with @cregox that one could argue that NodeBB isn't free, because you're paying for hosting it.

However, in the same vein, none of the service he mentioned are.

Well HE mentioned that none of them were free. But hosting something possibly costing you money is unrelated to the thing itself being free.

There are three key problems.... the one is that we are associating the cost of an action with the cost of an item, that can't work. That requires all kinds of illogical connections. For example, can jewelry not be free (or even exist) because it doesn't "do" anything? It just sits there. So since it does nothing, it can't be free? Clearly it can. NodeBB (and millions of other products) are free regardless of whether you want to run them, try to run them, etc. They simple "are free", even if you don't know about them, many of them are already free to you today. They are free regardless of anything you may or may not wish to use them in conjunction with.

The second is that there is an assumption that hosting is an intrinsic component of NodeBB. It's certainly the most common use example, but it is not the only function. NodeBB can be run locally on existing resources, for free. It can be read without being run, studied, copied, forked, or stored. Or just have ownership of. All those things are free use cases. Not that that matters, clearly, but it's important to note that hosting isn't a foregone conclusion.

The third is the notion that hosting can't be free. It is, in fact, often free. Rarely good hosting, but lots and lots of hosting is free. I actually run a provider that does free hosting, including of NodeBB (not for you people, it's for special cases, don't come asking for free hosting, lol). So it's almost important to note that just because the NodeBB team themselves don't make the hosting free, doesn't mean that it isn't. The same is try of the customization, find an intern willing to work for free, and that's free too.

Did you read my full post? Because that was kinda my point. You can argue that there are costs around NodeBB therefore NodeBB isn't free, but it's all really arbitrary because you can argue the same way about many different things that seem obvious. The question is where do you draw the line?
Because at some point everything will be paid and the word "free" becomes literally meaningless since there are no fully free things.

And usually, when talking about a specific product, where the costs are similar between different products within the same category, people draw the line on the cost of the product itself. Hell, often even if costs to run things are different, people consider only the cost of this specific product, not the cost to run it (for example, computers - I don't usually see people mentioning the power consumption as part of the price...).
NodeBB usually isn't free to run, but no forum software is, and some have upfront cost. So when asking "is NodeBB free" a reasonable assumption is that we don't count the costs to run it, since that's kinda the standard.

Especially since there is free hosting. I mentioned one example and linked to a list with some other possible options. And that's just stuff that's available for free to anyone, because sometimes there will be circumstances where you can get a better hosting for free - for example sometimes larger open source projects can get something like this free/at a discount (for example it's free at NodeBB Instant Hosting), something like GitHub Education for students, some friends or something.

And additionally, the actual price of paid hosting is not constant and not something that the creators of the product are responsible for. It all depends on hosting providers and your needs...

@oplik0 said in Some questions :

(I mean, except the time spent on it...)

I, for one, will agree with @cregox that one could argue that NodeBB isn't free, because you're paying for hosting it.
However, in the same vein, none of the service he mentioned are. On Facebook you're paying with your privacy, by viewing ads AND you're paying for a device capable of running a web browser or a facebook app!
Same thing applies to basically all services like that. You can't escape paying for something down the road, though sometimes the price is your time and attention or your data instead of money
That's why usually to consider something to be free people only consider the price of that thing by itself, and not other things that you might need for your use of the product.

For example - if you got a car without paying for it, would you not consider it free even if you didn't get lifetime supply of gas to go with it? I think most people would consider that car to be free.

Usually the same applies to software. Blender is considered to be free, despite requiring a powerful enough machine to run it which isn't free. You probably got your web browser for free - which is now basically taken for granted despite not having been common in the past - but you still need to pay for your computer, internet connection and electricity. And you most likely don't count these as a price of the browser.

Also, it actually is possible to host NodeBB for free.
Here is a quick example running on glitch: https://nodebb-example.glitch.me/
It's using free tier of MongoDB Atlas to store data, so the DB can grow to up to 512MB without incurring any costs. You can find the details, instructions and remix it here: https://glitch.com/~nodebb-example

Just a warning that this hosting is far from perfect - it has quite a few limitations and while you can work around most (for example apps being put to sleep after around 5 minutes without connections - just use a service like uptime robot to ping it every 5 minutes), it's still probably only a solution for really small forums.

You can find a few other services that might run NodeBB for free on free-for.dev but I just wanted to test glitch so that's what I used.
There are some guides for heroku, though I'm not sure if they work with the free tier ¯\_(ツ)_/¯

Hmm... I might check some other and create some guide on hosting NodeBB for free for small forums...

EDIT: also, just a note about this glitch instance - it has a few lines modified, though I'll have to look into it again since I was making the changes in the middle of the night, so I'm not entirely sure if the changes were necessary. But basically, nconf wasn't correctly configured to use environmental variables in at least one file that can be used to start NodeBB.
I think I'll check it later and make a PR to fix this

EDIT2:
Oh, I wrote most of it before the last comment here, so I'll also have to disagree with @julian - hosting can be free (as shown here) and custom development can be free too if you do it yourself

(I mean, except the time spent on it...)

And I'm actually net positive when it comes to spending money on hosting NodeBB, since the one bug bounty I got is still higher than what I spent on hosting NodeBB in total

Yes, ACP>extend>plugins>find plugins. You can install plugins from there.
Just a note that this only includes plugins published to npm with correct nodebb compatibility information in plugin.json and it might take a few hours to load a new version of the plugin if it's updated.

So it would seem that the maintenance mode is enabled despite being shown as disabled in ACP...
Could you perhaps try enabling it and if that doesn't change anything disabling it again? Perhaps changing the setting will fix the issue.

It's not a bug, it's a feature - you probably have maintenance mode enabled. Go to ACP>settings>advanced and disable it.

It should cache for an hour, I think (based on a quick look at nodebb package manager code). So yes - you have to wait a bit before the nbbpm refreshes. You can just install the updated version manually by using npm install <package name> from the command line in NodeBB folder.

I think you'll need to create that route in the plugin that you're using to add the custom field - NodeBB only provides routes for uid and username. You can check for privileges with middleware.canViewUsers if you don't want everyone to be able to see users info. I think the oauth plugin already sets up some custom routes, so you can base the api implementation on them.