NodeBB Development

I was looking through the docs, but could not find this. Sorry if I missed it. Is there a way to see how exactly the reputation system works, without browsing the source code? If I wanted to implement some very specific rules, how easy/hard is it to customize? Could I just write my own reputation plugin and swap it out?

@Baerrus oh ok thank you

I got it, now that I understand what installs redis. The way I upgrade is I create a brand new workspace, install a new version of nodebb, copy over the config.json. I think that makes sense in real deployment scenario versus executing "git pull" in place. This way I retain a fully functional prior version installation I can fall back to in a instant should something fail with a new version.

@baris I started working on a more SEO friendly theme/plugin. I hoped I could keep all the changes within a lavender derived theme, but I cannot. Some changes will be in the core. FOr example, server side rendered pagination. I am looking for some advice on how to coordinate making changes in a theme and core nodebb?

This was a setting under admin>settings>sockets it has been moved to config.json. Old name was websocketAddress now its just address under the socket.io object. Sample config.json { "url":"yourforum.com", "socket.io": { "address": "", //or url to socket.io server "transports": ["websocket", "polling"] } } Relevant commit: https://github.com/NodeBB/NodeBB/commit/14e46a87a63f5e983a58a73109710027297924f3 The reason is if you put a invalid value here sockets will not connect and since the admin page uses sockets to save settings you can't change it back.

Updated with header.tpl changes, relevant thread https://community.nodebb.org/topic/3488/header-tpl-changes

@peter setting the number of recent posts on the homepage to 0 got me my 100% usability on mobile. As it removes a lot of the padding issues that it complains about, read more being the main culprit. It's not big enough for mobile.

@a_5mith @Ted Thank you!

https://github.com/NodeBB/nodebb-widget-essentials/blob/master/library.js#L80-L113 Should give you some ideas, the active users widget changes behaviour based on where it is displayed, if its inside a topic it shows the poster in that topic, if its inside a category it shows recent posters in that category etc. widget.area.url gives the url of the page the widget is in.

@h_kirk said: I see the predicament. Nasty job to generalize that problem Strtolower solves 100% of issues.

@priapo At present, it's lower priority, as it's much easier to maintain the templates for NodeBB when they are all in English. However, if there is a need for it, then we will consider the demand when prioritising our tasks

Finally the pull request is open https://github.com/NodeBB/NodeBB/pull/2527. I'm out for today guys, hope you get everything. If not just ask, gn8.

@riteshsanap A bit of a hint can be found here

@Macrow-Willson said: Hi, just checkin in, I know Node can be quite clumsy in that matter and I am wondering how to deploy plugins on the production server, do i need to restart the entire instance? thank you! Just reload NodeBB from the ACP. Does the same thing, but doesn't take the site offline.

I figured out my issue... MongoDB user I was using had a readWrite role, but I guess it needs the dbAdmin role as well. When I tried creating a new user in the nodebb admin area, then it would make things go wonky without the dbAdmin role and result in invalid csrf tokens.

@BDHarrington7 If you're referring to the master-branch the problem is that you cache the value of var userExt = settings.get('strings.extensions'); (and some further operations) once at plugin-start and don't refresh those values after settings.sync(); (within a callback). So you need to re-calculate the regex variable within a callback for settings.sync.

ohhhh ok, got it! thanks @baris

nvm, I got it working. I was confused how async.each() worked..! here's what I ended up with: function getMainPost(topics, callback) { posts.getPostFields(topics.mainPid, ["content"], function (err, data) { topics.content = data.content; callback(null); }); } function getRecentTopics(category, callback) { categories.getCategoryTopics(category.cid, 0, parseInt(category.numRecentReplies, 10), uid, function (err, data) { var topics = data.topics; category.topics = topics; category.topic_count = topics.length; async.each(topics, getMainPost, function (err) { callback(null); }); }); } async.each(categoryData, getRecentTopics, function (err) { next(err, categoryData); });

@pitaj Yes, isAdmin() is the middleware, whereas isAdministrator is the library method. They are functionally similar, except the middleware handles redirecting the user to 403