Great Idea! I took your solution and added a few lines of CSS to hide the downvote arrow and remove the whitespace.

// Change the icon for votes
span.votes {
    // not voted is outline heart
    .fa-chevron-up:before {
        content: "\f08a";        
    }
    // upvoted is solid heart
    .upvoted .fa-chevron-up:before {
        content: "\f004";
    }
}
// hide the downvote element to remove whitespace
a[component="post/downvote"] {
    display: none;
}
// reduce margin of post-submenue for alignment 
.topic .moderator-tools {
    margin-left: 0px;
}

@PitaJ I have exactly the same Problem. Custom Javascript is gone after updating to 1.7.3. Custom JS und header tab are empty. Is there a possibility to recover that code?

Thank you, guys! npm i was the solution.

Hello everybody,

I'm trying to upgrade nodeBB from 1.6.1 to 1.7.3. After git fetch and git reset --hard origin/v1.7.x I tried to run ./nodebb upgrade, but I get the following error message:

package.json not found.
Populating package.json...
OK
module.js:538
    throw err;
    ^

Error: Cannot find module 'graceful-fs'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/path-to-nodebb/NodeBB/src/file.js:10:16)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)

Thanks for any help!
Christian

Thank you @PitaJ and @baris ! It was the plugin. I had installed the 1.2.1, but it does not worked. I uninstalled the plugin and registration i working fine again.

@pitaj here is the nodebb-log. Actually nodebb crashes after submitting the register form.

17/10 20:53:30 [11178] - error:  TypeError: Cannot read property 'username' of undefined
    at /home/user/nodebb/NodeBB/node_modules/nodebb-plugin-registration-notification/library.js:78:52
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:3861:9
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:421:16
    at iterateeCallback (/home/user/nodebb/NodeBB/node_modules/async/dist/async.js:928:24)
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:906:16
    at /home/user/nodebb/NodeBB/node_modules/async/dist/async.js:3858:13
    at /home/user/nodebb/NodeBB/src/database/mongo/sorted.js:64:5
    at handleCallback (/home/user/nodebb/NodeBB/node_modules/mongodb/lib/utils.js:120:56)
    at /home/user/nodebb/NodeBB/node_modules/mongodb/lib/cursor.js:860:16
    at handleCallback (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:171:5)
    at setCursorDeadAndNotified (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:505:3)
    at nextFunction (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:651:7)
    at Cursor.next [as _next] (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:692:3)
    at fetchDocs (/home/user/nodebb/NodeBB/node_modules/mongodb/lib/cursor.js:856:10)
    at /home/user/nodebb/NodeBB/node_modules/mongodb/lib/cursor.js:879:7
    at handleCallback (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:171:5)
    at nextFunction (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:682:5)
    at /home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:593:7
    at queryCallback (/home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/cursor.js:253:5)
    at /home/user/nodebb/NodeBB/node_modules/mongodb-core/lib/connection/pool.js:469:18
    at _combinedTickCallback (internal/process/next_tick.js:95:7)
    at process._tickCallback (internal/process/next_tick.js:161:9)
17/10 20:53:30 [11178] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
17/10 20:53:30 [11178] - info: [app] Database connection closed.
17/10 20:53:30 [11178] - info: [app] Web server closed to connections.
17/10 20:53:30 [11178] - info: [app] Shutdown complete.
17/10 20:53:37 [8701] - info: Initializing NodeBB v1.6.1 http://my.domain.de
17/10 20:54:03 [8701] - info: [socket.io] Restricting access to origin: http://my.domain.de:*
17/10 20:54:07 [8701] - info: Routes added
17/10 20:54:07 [8701] - info: NodeBB Ready
17/10 20:54:07 [8701] - info: Enabling 'trust proxy'
17/10 20:54:07 [8701] - info: NodeBB is now listening on: 0.0.0.0:63536

Hello everyone,

I have a problem with the registration. No registration could be completed. Everything is fine (inline validation etc.) till the submit-button is pressed. After that, the page reloads and the following error message is shown:

Registrierungsfehler
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>502 Proxy Error</title> </head><body> <h1>Proxy Error</h1> <p>The proxy server received an invalid
 response from an upstream server.<br />
 The proxy server could not handle the request <em><a href="/register">POST&nbsp;/register</a></em>.<p> Reason: <strong>Error reading from remote server</strong></p></p> <hr> <address>Apache/2.2.15 (CentOS) Server at my.domain.de Port 80</address> </body></html>

and this error is in the browser console:

jquery.js:9566 POST http://my.domain.de/register 502 (Proxy Error)
send	@	jquery.js:9566
ajax	  @	  jquery.js:9173
e.fn.ajaxSubmit	@	jquery.form.min.js:7
(anonymous)	@	register.js?v=4r12ck8gj25:1
(anonymous)	@	register.js?v=4r12ck8gj25:1
i.onack	@	socket.io.js:2
i.onpacket	@	socket.io.js:2
(anonymous)	@	socket.io.js:2
i.emit	@	socket.io.js:1
i.ondecoded	@	socket.io.js:1
(anonymous)	@	socket.io.js:2
i.emit	@	socket.io.js:1
f.add	@	socket.io.js:1
i.ondata	@	socket.io.js:1
(anonymous)	@	socket.io.js:2
i.emit	@	socket.io.js:1
i.onPacket	@	socket.io.js:1
(anonymous)	@	socket.io.js:1
i.emit	@	socket.io.js:1
i.onPacket	@	socket.io.js:2
i.onData	@	socket.io.js:2
ws.onmessage	@	socket.io.js:2

and on the serverside i have these errors:

[Tue Oct 17 12:33:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] (20014)Internal error: proxy: error reading status line from remote server localhost, referer: http://my.domain.de/register
[Tue Oct 17 12:33:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] proxy: Error reading from remote server returned by /register, referer: http://my.domain.de/register
[Tue Oct 17 12:38:23 2017] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:63536 (*) failed
[Tue Oct 17 12:38:24 2017] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:63536 (*) failed
[Tue Oct 17 12:38:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] (20014)Internal error: proxy: error reading status line from remote server localhost, referer: http://my.domain.de/register
[Tue Oct 17 12:38:59 2017] [error] [client 2003:61:4962:1333:c54c:4556:b5aa:ddac] proxy: Error reading from remote server returned by /register, referer: http://my.domain.de/register

I'm pretty sure, that the registration was working before I upgraded to 1.6.0 Did you changed there anything in this process?

Everything else is working fine. Creating posts, chat, upload files, upload and change profile images etc.

On the serverside I have to use not the perfect configuration with apache 2.2 (without mod_wstunnel), but it worked pretty well.

Thanks for any help,
Chris

Thank you @PitaJ and @julian for your support! Everything works fine now.

The error was because of a wrong security option in the settings and the speed of sendmail increased by itself. Probably there was a problem on the shared server during my first test.

Keep up the great work! NodeBB is really great!

Hi @PitaJ, I did the Upgrade to 1.6.1 and after a few hickups nodebb can send mails again, but only with the internal mailserver. The external option is still broken. Sending Mails via the internal mailserver is quite slow.

Here is the Error-Message, which I get when I try the externl mailserver option:

io: 2 on [ { type: 2,
    nsp: '/',
    id: 14,
    data: [ 'admin.email.test', { template: 'welcome' } ] } ]
12/10 12:38:27 [18738] - error:  Error: 140483857790752:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:797:

@pitaj thank you for the information and I hope that the fix will work for us, too!