Best Forum Software – NodeBB

Already in 2015. Maybe again in 2017?

How can I vote for NodeBB on the CMS Critic site? Please, explain like I'm five.

@MJ CSS? Nah. Just execute some JS
For example:

$(window).on('action:widgets.loaded', function () {
	$('li[component="categories/category"]')
	.add('li[component="category/topic"]')
	.find('.stats > small')
	.each(function (i, el) {
		var
			$small = $(el),
			text = $small.text(),
			$icon,
			iconClass

		if (text === 'Topics')
			iconClass = 'fa-group'
		else if (text === 'Posts')
			iconClass = 'fa-group'
		else if (text === 'Views')
			iconClass = 'fa-group'
		else
			return

		$icon = $('<i class="fa fa-fw ' + iconClass + '"></i>')
		$small.replaceWith($icon)
	})
});

P.S. Actually, the best way to change something in a theme - is to fork the theme and make whatever changes you want in your own repository. But you'll have to keep track of any new changes from the original theme repository, resolve merge conflicts, etc. This way is a hard way. The example I've provided above is the easy one.

@Popatop15 I'm sorry, but it's near to impossible. Take a good look at those examples https://github.com/NodeBB/NodeBB/tree/master/src/database

The differences between MySQL and any noSQL databases are huge.

NodeBB architecture was designed with Redis in mind. Redis it's not even a database at all, it's an advanced key-value store (completely noSQL). So, it's relatively easy to make a driver for a noSQL database, like MongoDB. But it would be way too hard to implement that kind of a driver for a relational database, like MySQL.

Just to be clear - even though, strictly speaking, it is possible to make the driver, NodeBB won't be working good with it anyway.

Personally I'd suggest you to spend some time to learn how to work with MongoDB, if you still unfamiliar with it. MongoDB is very popular nowadays and working with it is much easier than with anySQL database. If you're an expirienced dev, you can become a ninja in just one week.
Then, you'll be able to make an effective bridge between Mongo and MySQL parts of your applications.

p.s. Just in case, I want to mention that everything is possible.

npm i redis --save

@frissdiegurke open the console in browser and type config['theme:id']

I'd like to participate

I just wonder, whether someone is interested in a guide of automatic incremental backing up NodeBB using rsnapshot on Linux-based servers? I mean not a tool, but a guide only. Because I have no intention yet to make neither the tool nor to contribute to the nodebb-backup tool.

And if I'll make the guide someday, it probably will be not for complete newbies, but for those who's able to (at least):

1. use terminal
2. completely understand what chown and chmod commands are for, and what * * * * * in cronejobs mean

p.s. When you're using rsnapshot, there is almost no difference which database you're using, Redis or MongoDB.

@askar said:

How many instances can I install on 512Mb RAM digitalocean droplet?

One at least

If you'll use Redis, and your forums will have less than 100k messages each, probably two
If you'll use Mongo, in the same circumstances, maybe even three instances

However, I'd recommend you to use 512MB droplet for each instance

@scottalanmiller said:

That's a weird one.

Truly.
The weirdness is in fact the error comes randomly O_o
Steps to reproduce: continue pressing a "Page Reload Button" (Ctrl + R?), one per 10-20 attempts you'll catch the error. No matter what page you are on, even ACP.

And not only the one error, some others too
https://a.pomf.se/pidgjn.png

@Rex-Huang I faced the same error when I've made fork of the plugin.
I found a way, how to get it work... Maybe it may be useful for you.
https://github.com/MegaGM/nodebb-plugin-emailer-yandex/blob/master/index.js#L23-L26

@Firelad Did you uncheck the checkbox?
ACP > Settings > User > Convert profile image uploads to PNG

@gvimlan You can listen to the filter:user.updateProfile hook
https://github.com/NodeBB/NodeBB/blob/master/src/user/profile.js#L21
and restrict email changing.

UPD: You see that conditional statement, right?
https://github.com/NodeBB/NodeBB/blob/master/src/user/profile.js#L38-L40
You need to just always make it = null; inside your listener, that's it.

@psychobunny said:

Sounds like a cool idea.

Yeah, definitely.

@Andrew-Stover said:

focus is building widgets

(and/not) plugins?

@Nicolas The reputation placed not only in users objects, but in an additional "separate table" also.
/users/sort-reputation controller uses that "table".
https://github.com/NodeBB/NodeBB/blob/master/src/controllers/users.js#L54

@Codejet I'm making kinda similar plugin right now.

The plugin's goal is to show only one badge with a "most high priority".

Let's say a user is in three groups:
"Officer" (group's weight: 60)
"Recruiter" (group's weight: 55)
"Regular" (group's weight: 50)

Regardless of what was choosen in UserSettings as a badge, only "Officer" badge will be shown, 'cuz that group has higher priority than others.

And the question "Why users are in multiple groups?": Because of ability to manage those groups' membership.

@Codejet said:

what code would I add to the template if I wanted at least 2 badge's displayed in my posts.

You need to make and register a new template helper, for both clientside & serversde, and execute some magic inside.
I can help you via Teamviewer, if you please ^.^

@limker You can install nodebb-plugin-colors then add white colored points, as many as you want

@julian said:

I suppose the thing is over 95% of the population wouldn't even go as far as to clear their cookies

Me too. I wouldn't clear cookies, I'd just press Ctrl + W.

@Mega said:

I'll check that today-tomorrow and will post here.

aight
doesn't reproduced anymore on latest

@julian said:

Can't reproduce on MongoDB or Redis.

I was able to reproduce that bug 2 days ago. Steps to reproduce were: Going to any page in ACP via ajaxify

I'm pretty sure, it was because of the error of requiring ../utils on the client-side. 'cuz these and some others bugs weren't appeared on cold-load, but on ajaxify they were.
I didn't interacted any NodeBB installation for approx 2 days, perhaps these bugs indeed were fixed by someone already. I'll check that today-tomorrow and will post here.