@pichalite Thank you!

So, on a fresh install of version 1.1.0 when clicking on the upvote/downvote buttons I get this:

I've also tried on the weekly builds with the same result. Any ideas what might be causing this?

@yariplus Yes of course

@pichalite I will attempt an upgrade to 0.9.x see if it fixed the issue. Thanks a bunch!!

Anyone? This is a pretty major thing for us :S

@pichalite http://forums.eternalgames.net/

Hey all, there seems to be a problem with group permissions on my forums. For some reason, users are able to join private group without being accepted which is quite a problem as we have ~3k users and this sort of thing can become unmanageable very quick. We use groups on the forums for our staff members and they have special permissions to moderate topics etc..

I also noticed that when removing a user from said groups, I get a Error: Invalid data alert but the user does get removed from the group. Something is wrong but I cannot pinpoint what exactly and nothing shows up in the logs.

We are running 0.8.2 currently. Any help would be appreciated! If you need more information please ask and I shall oblige

@ffmad Looking good

This is cool as heck, could you share the code used to achieve this? I'm interested in having this on my forum as well

I'm having a similar error while trying to install NodeBB with Mongo.

Here's the full log:

Welcome to NodeBB!

This looks like a new installation, so youll have to answer a few questions about your environment before we can proceed.
Press enter to accept the default setting (shown in brackets).

8/11 20:06 [10508] - info: Now configuring mongo database:
Configuration Saved OK
npm WARN peerDependencies The peer dependency kerberos@~0.0 included from mongodb-core will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.

> [email protected] install /home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos
> (node-gyp rebuild) || (exit 0)

make: Entering directory '/home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos/build'
  CXX(target) Release/obj.target/kerberos/lib/kerberos.o
In file included from ../lib/kerberos.cc:1:0:
../lib/kerberos.h:5:27: fatal error: gssapi/gssapi.h: No such file or directory
compilation terminated.
kerberos.target.mk:94: recipe for target 'Release/obj.target/kerberos/lib/kerberos.o' failed
make: *** [Release/obj.target/kerberos/lib/kerberos.o] Error 1
make: Leaving directory '/home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/mboisvert/Documents/nodemongo/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.2.5-300.fc23.x86_64
gyp ERR! command "/usr/local/bin/node" "/home/mboisvert/Documents/nodemongo/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/mboisvert/Documents/nodemongo/node_modules/mongodb/node_modules/kerberos
gyp ERR! node -v v5.0.0
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok 
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/jade requires mkdirp@'0.3.0' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/mkdirp,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt requires async@'~0.1.22' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/async,
npm WARN unmet dependency which is version 1.4.2
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt requires colors@'~0.6.2' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/colors,
npm WARN unmet dependency which is version 1.1.2
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt requires rimraf@'~2.2.8' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/rimraf,
npm WARN unmet dependency which is version 2.4.3
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-legacy-util requires async@'~0.1.22' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/async,
npm WARN unmet dependency which is version 1.4.2
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/argparse requires underscore@'~1.7.0' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/underscore,
npm WARN unmet dependency which is version 1.8.3
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-legacy-log requires colors@'~0.6.2' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/colors,
npm WARN unmet dependency which is version 1.1.2
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-legacy-log-utils requires colors@'~0.6.2' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/colors,
npm WARN unmet dependency which is version 1.1.2
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/grunt-contrib-watch requires async@'~0.2.9' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/async,
npm WARN unmet dependency which is version 1.4.2
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/mocha requires mkdirp@'0.3.5' but will load
npm WARN unmet dependency /home/mboisvert/Documents/nodemongo/node_modules/mkdirp,
npm WARN unmet dependency which is version 0.5.1
[email protected] node_modules/connect-mongo
└── [email protected]

[email protected] node_modules/mongodb
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected])
├── [email protected] ([email protected])
└── [email protected] ([email protected])
/home/mboisvert/Documents/nodemongo/node_modules/mongodb/lib/mongo_client.js:437
              throw err
              ^

TypeError: _.assign is not a function
    at new MongoStore (/home/mboisvert/Documents/nodemongo/node_modules/connect-mongo/lib/connect-mongo.js:114:19)
    at /home/mboisvert/Documents/nodemongo/src/database/mongo.js:111:27
    at /home/mboisvert/Documents/nodemongo/node_modules/mongodb/lib/mongo_client.js:434:15
    at doNTCallback0 (node.js:428:9)
    at process._tickCallback (node.js:357:13)

Additional information:
OS: Fedora 23
NodeBB: 0.9.0 cee3918e9b8096e421933678178ddfe4e3b71adf
Node: 5.0.0

@psychobunny Done! https://github.com/NodeBB/NodeBB/issues/3804

@Kowlin Hmm I see, thank you for your reply. What do you mean by unused image? This particular one I posted is my own (I am active daily) which I tested after reports from users not being able to change their picture.

Could this be the source of the problem or is it something else? I'm not seeing anything else in the logs. I should also note that we are using nodebb-plugin-imagemagick and have "Convert to PNG" enabled in the user settings.

Alright so basically, everything was working fine until we pulled the git repo from master on Monday (perhaps we shouldn't have?). I do not have access to the server console so I cannot tell you precisely which git hash we're on.

Since then, users on our forums cannot change their account pictures. This pops up in the NodeBB log everytime a user tries to change their picture:
29/10 14:06 [15435] - error: unable to delete picture /tmp/ZBXRoFYlE-3oKz3fQst8hjbH.jpg

Could it be a permission issue? Or is it an issue with NodeBB itself?

Interesting! Is this on master already?

Hello all, I know my choice of title might sound a bit confusing but let me explain further. Basically, I'm trying to display links to subcategories under a parent category a bit like this:

Now, after a bit of digging around, I did find a sort of solution to this which resulted in this which is what I want, however not there:

This is fine except it only works for the topmost parent categories with the code that I've found which I simply inserted in my templates/categories.tpl

Essentially, I would like to display the links to subcategories of the subcategories (2 deep) of "Exode" and "Eternal Dragon Nest" which I believe should be in the templates/category/subcategory.tpl or templates/categories/item.tpl templates but I am not sure.

Can anyone enlighten me with their knowledge?
Sorry for being such a n00b!

I run the VPS SSD plan on OVH for my forum with Ubuntu 14.04 and everything is working very well

@baris That would be awesome and would help us greatly!

@psychobunny What @Kowlin pointed is correct and does apply to us. We run a gaming community and have multiple games which each need separate Announcement, Updates, etc.. sections.

Currently, if you have multiple categories with the same name it can be very difficult and confusing to differentiate them. It would be great to have some way to distinguish which categories are where.

See picture below:

This is something I've been wanting for a while now but it would be great if we could copy all the privileges from a category to another category.

A use case for this is for example, I have multiple "moderator" groups on my forum so instead of going and editing every single category I have, I set the permissions in General and then edit my other categories to pull in privileges from General.

EDIT: Additionally, it could be very useful to have the option to apply the privileges from a parent category to all of it's child categories.