.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'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

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.

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

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.

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

@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.

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.

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.

Masz na pewno dobry url strony w config.json?
Musi on zawierać także http:// lub https:// z tego co pamiętam.

@shanza97 did you build NodeBB and restart? Aside from "restart" there should be "rebuild and restart" button in acp. Or you can manually trigger it from cli: ./nodebb build and ./nodebb restart.

Then you will probably have to modify the sso plugin to reject or truncate usernames that are too long.

I'm not sure if NodeBB should reject things like creating an user by a plugin if the plugin doesn't adhere to admin settings, because there might be valid reasons for doing it. For example - you might have a username length limit, because you want to reserve longer usernames for bot users created by a plugin or something.

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.

@Brutus5000 said in How to change user name via external call?

2. I have no clue how to do this with the plugin system. From my understanding the hook system can only be triggered when actions are executed inside nodeBB. But in this case the action would be triggered from a 3rd party system without a user being logged in.

Well, fortunately for you, you are wrong. Hooks are really just triggers - if x happens call every function that is using that hook. But there is no problem with using something else to trigger your plugin.
A relatively common example would be websockets, that can be used to send data from frontend to backend when there is no hook covering what you want to get.
Example: https://github.com/NodeBB/nodebb-plugin-category-notifications/blob/master/lib/websockets.js

So as long as there is a way to communicate between your service and your NodeBB plugin there shouldn't be any problem there.

Now, as for

1. I have not seen any documentation on changing usernames via plugin.

Unfortunately, there is not a lot of documentation on NodeBB internals so you mostly need to just look at the source and find what you need.
In this case the functions you need are in src/user, so you can import them with const user = require.main.require('./src/user');.
To update the username you will need a function from src/user/profile.js - user.updateProfile.
But to do that you will need their uid - while I assume you only start with their (old) username. Fortunately there is a function getUidByUsername in src/user/index.js that works just like the name suggests.

There is also another way to do what you want, however. There is a (write api plugin)[https://github.com/NodeBB/nodebb-plugin-write-api] you can use to change the username without writing your own plugin. Just get the uid from the standard read api (your.forum.com/api/user/userslug) and then make a PUT request to your.forum.com/api/v2/user/:uid (replacing :uid with the uid from the previous step, obviously).

@PitaJ said in change http to https but cannot login:

When I visit your site through https I get a "this connection is untrusted" error meaning your TLS stuff is not set up correctly.

To be more specific - the website is using a self-signed certificate, so it's not signed by any trusted CA and browsers really don't like these certs (for good reasons, but still - it's annoying in some cases).

Other than that tls seems to be correctly configured and would get an "A" in Qualys SSL test.

I'm not sure if untrasted cert would cause any problem like that. Or at least - it shouldn't, because this kind of certificate is useful for testing, where you can can manually decide to trust your certificates, as you control the client machines

@巫易澄 if the rebuild didn't work, look for trailing/leading spaces in your keys. If I remember correctly sometimes when copying from Google console I'd get these and they'd break things in plugins using these keys (broken sso with this plugin, or even non-functional forum with yourube-embed. Had to disable the plug-in server-side...)

You have to create an acp page for managing your plugin.
For a basic example just look at how the quickstart plugin implements its panel, and look for plugins that have a panel similar to what you want to do.

@y-h #red is not a color (just red is), but other than that I can assure you there is nothing wrong with this CSS and the problem lies elsewhere:

Custom CSS:

With the original transparent color:

Do you have Traffic Management module turned on? (admin/settings/advanced)
Because it sounds like you want basically what it's supposed to do. I don't know how well does it work, because I haven't had any RAM problems regardless of it being turned on or off, but you might want to try tweaking its settings before making a custom solution.

Where did you put it? It seems to work fine for me when I put it in custom css in ACP.