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?

Hello everyone, I urgently need a fix to facebook/twitter/google-sso. They're broken for invite only/registration queue settings.

It's fairly straightforward to see the bug (the code for different behaviour on registration settings is in the registration page itself, not in the "user.create" function).

I don't even need the full fix since I'm using the admin-only invite so I was thinking of forking these three plugins. But then it seems I'll lose the entire plugin update infrastructure within the admin pages.

What's the best way of handling it? I haven't even started on any plugin dev yet so I don't know how to set things up honestly. Suggestions?