I'd like to be able to decide what categories users are automatically subscribed to. I know there's a plugin to prevent new users from automatically subscribing to all categories, but I'd prefer a lot more granularity than that.

Help?

Turns out mail fails when I run nodebb using ./nodebb start but not as a service. I'm not sure why...

@julian I don't even see any hint that there is an attempt to contact gmail. And I already did the work to make sure gmail worked. I've had it working consistently since 1.3.x. It broke on the 1.5.x -> 1.6.0 upgrade.

It's like the mail queue isn't even processed. Is there some way I can debug it?

I have issues with gmail sends too. I don't see any errors... just nothing happens.

Is there a changelist somewhere regarding what's new in 1.2.0?

@baris What about this site, is it running the latest or 1.1.2? I can't reproduce it here.

On my install, I have the following issue:

1. Start a new topic, or reply to a current one.
2. Edit the content, save.
3. The updated content is now visible.
4. Reload the page - the original content is now shown.
5. Open edit - the result of the latest edit is now shown.
6. Save without making any changes - see that the updated content is now visible (again)
7. Reload - the original version is again shown.
8. Restart NodeBB
9. Open the topic - see that the edited version is now shown ok.

So I can only get edits to correctly show on the front page with 1.1.2. I'm using MongoDb if that makes any difference?

@phit can you explain how you mean?

I needed two customised plugins for our forum (one scaled back FB SSO and one for bulk user creation). Initially I had huge problems making the plugins actually show up. I ended up adding symbolic links to each from node_modules.

That way they showed up as "installed" and could be activated.

However, is this really "the right way" of doing it? The docs say use "npm install" (which installed the dependencies but not much more). What's the proper way of deploying a plugin that's not made for public use?