@zenkamal said:

2. None of the topic lists have a "New Topic" button (hence the widgetized homepage also doesn't have one with the recent view list). Is it possible to add the "New Topic" button to each page (recent posts and popular posts), or manually add it to the custom home page?

Great plugin, very useful, however I get the same issue above. Is there a work around/fix for this? How to get the New Topic button's back?
To be clear, there are no New Topic buttons on any category pages. Tried playing with the AccessControl, and that did not change anything...

EDIT:
Did a fresh install with 0.4.x and seems to be working ok.

Thanks for the reply @a_5mith.

I still feel a better user experience would be to give some feedback and not flush all their input fields forcing them to fill it all in again. Real potential to lose new sign ups this current way. So am I right to assume that there has never been any messaging for this, and I should add from scratch?

Drifting off topic, but:

The only difference is username when registering using oauth, which adds a string to the username to avoid conflicts.

According to the source code, this appears to always be the functionality, even without oauth. I have edited my fork to not do it. It would be nice if there was an on/off option.

On my dev 0.4+, and also on this (community.nodebb.org) site:

Attempt to register with an email address that already exists (or any criteria that would cause registration to fail). Click [register now] and the registration input fields just clear and no message is given. The user does not have any indication of what went wrong.

I have never observed any registration failure messages, so I am guessing something is broken/missing.

If anyone else needs the (nicer) fix, here it is:

npm install git+https://github.com/SPHINX--/nodebb-plugin-emailer-local

Debugging complete. Found the following error: 503 AUTH command used when not advertised

So to hack a fix, I had to comment out the 'auth' portion of the nodemailerTransport config object in index.js (lines 24-27).

Long route to get there, but emails are now working.
Thanks for your help. Hopefully things are smoother with the next stable release.
I should probably fork and do a nicer fix for others to use. Will add to my todo list.

Right, so from the log:

warn: [emailer.smtp] Unable to send reset email to uid 2!!

No sign of any emails making it out of NodeBB.

I am using exim4 (locally obviously). Sending from a shell prompt using the 'mail' command works fine, so I have to assume it works.

Best way to debug NodeBB issues?

Settings page now visible for emailer local.
Still waiting for an email to make it through to confirm things are working.

@julian Perfect. That will do it. Installed. Now testing...

Hold on, might have found something on my end...
Yes, firewall blocking the git port. Fixing...

@julian Tried again, still get the same error for his fork:

npm install --verbose git://github.com/psychobunny/nodebb-plugin-emailer-local
...
npm verb lock git://github.com/psychobunny/nodebb-plugin-emailer-local /root/.npm/686ec736-unny-nodebb-plugin-emailer-local.lock
npm verb addRemoteGit [ 'git://github.com/psychobunny/nodebb-plugin-emailer-local',
npm verb addRemoteGit 'master' ]

@julian said:

nodebb-plugin-emailer-nodemailer

If I try: npm install nodebb-plugin-emailer-nodemailer

I get: npm ERR! 404 'nodebb-plugin-emailer-nodemailer' is not in the npm registry.

@psychobunny
npm install git://github.com/psychobunny/nodebb-plugin-emailer-local
seems to hang at:

npm verb lock git://github.com/psychobunny/nodebb-plugin-emailer-local /root/.npm/686ec736-unny-nodebb-plugin-emailer-local.lock
npm verb addRemoteGit [ 'git://github.com/psychobunny/nodebb-plugin-emailer-local',
npm verb addRemoteGit 'master' ]

Any advice? Anyone successfully used this fork?

Switching to the hash version given, fixes it. Thanks.

Yes! Very useful.

Fair enough. I will start reviewing the code base when v0.4 comes out.

ACP option to enable/disable username changing is a must for us.
A username black list and alpha numeric character set restriction is also very important.
Please add if you get a chance, otherwise we will have to hack it in ourselves before going live.
Regardless, fantastic product. Keep up the good work, looking forward to v0.4.