Running it with ./nodebb dev should give you a more detailed output.

@a_5mith said:

But mod status may be a bit much for some admins to just give out without fully looking into who it should go to.

An alternative would be to move the user to an arbitrary group when a certain level of reputation has been acquired. This arbitrary group could still be Mod, but it would also allow for the relatively common "New Members" group that has several restrictions which users are placed in until they have at least a certain amount of something. (usually posts or likes or in this case reputation). Alternatively, you could also require an admin/existing mod to review the promotion before it is executed.

@julian: Having multiple margins for pro/demotion would also be neat. For example, > x rep = "Assistant" rank, > y rep = Mod rank, < z rep = the "Enjoy your increased flood delay timer" rank

@shady2k said:

@Xiph, I can't make it work with subdomain. Websocket's querys gets error with Invalid uid = 0. Could you describe your config?

Supposing your site is example.com and the subdomain you used for websocket is websockets.example.com:
Go into the admin control panel on your NodeBB site, then go to Settings > Advanced and ensure that underneath the "Set domain for session cookie" you've written .example.com (note the first dot). Click "Save Changes", clear your cookies and log in again. That's what solved it for me.

@Jelena said:

Is there a way to separate first post from others on post page? I want to move their positions, like on facebook for example. First post will be main post and others for example to be listed on it's right side as comments. I couldn't understand how to do that cause it seems like they all have the same code.

You can either just address the first post separately with a more specific css selector (i.e. .topic .posts > li.post-row[data-index="0"]), or if you'd like to go one step further you can check for @first while looping through the posts array in the topic.tpl template.

Using Bootswatch skins the chat bar looks kinda funky now: http://i.imgur.com/cb0fM3v.png it only covers about half of the screen and just looks weird in general =/

Also the vertical bar next to the topics in /unread and /recent is always grey even if the topic hasn't been read yet, makes it look kinda boring.

It should be in the Thread Tools menu, which is generally located (depending on your theme) above and/or below the first post in a thread.

Right before running ./nodebb setup, you're supposed to run npm install, which also fetched the Lavender theme.
If, for some godforsaken reason, you remove stuff between these two commands, you should run npm install again because it installs all the packages that are needed to get NodeBB to initially work and install. Because Lavender is the default theme and is guaranteed to be installed if you actually follow every setup guide that's around, this fails without Lavender installed, just like it would fail without the bcryptjs and gravatar packages installed.

If you want to modify database settings on an already existing installation, just modify config.json instead of running the installer all over again. The installer is for just that: installing. Not for modifying any other settings on an existing installation.

In order to prevent people from registering loads of accounts just to get someone to Mod status, you might also want prevent people with < x reputation from giving others reputation. Or, maybe a bit more elegant, not count their upvotes and downvotes towards people's reputation until they have at least x reputation themselves.

You'd have to manually create each and every user, but aside from that it's perfectly possible to disable registration and restrict access to all subforums to members only.

@Scuzz said:

Can someone explain to me what exactly the local login is?

Local login is the user/password authentication mechanism NodeBB uses by default. Disabling it removes the ability to login unless you have a plugin installed that provides an alternate method of authentication (i.e. logging in with your Google or GitHub account).

@yariplus said:

Hmm, tried on a fresh install, but lwip wouldn't build for me.

Most likely this would be because all native modules need to be updated for 4.0.

Quoting from a blog post:

Recent changes to V8 which are included in io.js v3 are much more profound and require not only a newer version of NAN but a breaking API change in NAN itself which requires code changes in all dependent native modules.

(NAN = Native Abstractions for Node)

Some modules are already compatible though, as the same version of NAN is used by both io.js v3 and Node.js v4 and io.js v3 has been out for a while, so module authors had some time in advance of v4 to upgrade.

@meetdilip said:

@Xiph said:

You'd have to manually create each and every user, but aside from that it's perfectly possible to disable registration and restrict access to all subforums to members only.

Thanks. Can you tell me where disable registration option is ?

Admin Panel -> General Settings -> User -> Allow Registration

@psychobunny said:

@Nicolas said:

@psychobunny Also I'm going to create another plugin, and I need this space in user's profile. Do you have any suggestions how I can reach it without manual editing also?

Sorry I missed this. We should add more hooks (or widget areas) in the profile section. This is way better than requiring people to edit the template for sure. If you make a PR to add that functionality I'm sure we would accept it

How about giving plugins a way to specify some markup that'd added before/after every partial?
i.e. nodebb-theme-persona/templates/partials/topic/post.tpl existing would add a hooks/widget areas/whatevs. like before:topic-post and after:topic-post?

@meetdilip

• .jpg: Does not support transparency, generally uses lossy (= loss of quality) compression. Said lossy compression is actually optional, but most image editors apply it by default when saving in .jpg format and once this loss of quality has occurred (i.e. in an image fetched from the 'net), it cannot be reversed.
• .png: Supports transparency, lossless (= no loss of quality) compression. Due to this however, bigger images tend to have a larger file size in .png than they do in .jpg.
• .svg: File format for vectored images. Scales infinitely (= maximum quality, so matter the size you display the image at or the quality of the screen (i.e. normal DPI vs. Retina). Generally has a small file size. Not supported in IE8 and earlier.

would be neat.
Also having an unread attribute on topics on the /recent page and in categories (or just every page that contains a listing of topics, really (and maybe also on the topic itself? ) would be nice.

@RazorAxis said:

I am having an issue with mobile when I try to add a side bar of recent topics on the home screen. Comes out ok on desktop but instead of reverting to the bottom on mobile it just over lays ontop of the categories...

I've had fairly similar issues with widgets in the header, although this PR fixed those.

@xbenjii said:

@a_5mith said:

@bentael, any chance akismet can be trained to look at the topic title as well as the post content. Current spam is only in the title. Whether the title is included in post content or something like that.

Could it be something as simple as changing

comment_content: data.content,

to:

comment_content: data.title + data.content,

As the title could be considered a top-level header, how about we add a couple newlines?

comment_content: data.title + "\n\n" + data.content,

@arasbm said:

I like being able to quickly open developer tools on any friends machine when I see an issue and start inspecting.

I stay the away from my friends' machines, or else they start expecting me to magically fix everything for them haha.
Though I do hope they make the Developer Edition portable by default, so I can just put it on a USB stick in my pocket. Or else I might have to add it to a Tails ISO =P

Since they're global, it doesn't seem to make sense that they're reloaded every time you navigate to a different page.
Would save a few reflows if they were persistent like the navbar.