After last restart forum has been up almost 2 days without crash, no plugin has been disabled. Actually I didn't do anything else, just started NodeBB again.

At least emojis in link do not crash markdown (i tested this at own local installation first ).

Should this be reported to GitHub as separated issue?

# Example for markdown :smile: 
[test](http://www:heart:com)

Only default? plugins, haven't installed or deactivated any, default set was also used with 1.5.0

• nodebb-plugin-composer-default
• nodebb-theme-persona
• nodebb-plugin-markdown
• nodebb-plugin-mentions
• nodebb-widget-essentials
• nodebb-rewards-essentials
• nodebb-plugin-soundpack-default
• nodebb-plugin-emoji
• nodebb-plugin-emoji-extended
• nodebb-plugin-emoji-android
• nodebb-plugin-emoji-one
• nodebb-plugin-ns-awards
• nodebb-plugin-spam-be-gone
• nodebb-plugin-google-analytics
• nodebb-plugin-dbsearch

After neglecting upgrades so long I upgraded to newest versions, to fix broken bootstrap links. All went better than last update from 1.1.2 to 1.5.x. First I did backups, and test upgrade, and then live version, all ok. Now about 12 hours later forum crashed.

I also upgraded Node to newest LTS version (8.11.1), previous version was running with 6.x.

At log I have 4 of these:

2018-04-07T11:10:49.148Z [39] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
2018-04-07T11:10:49.147Z [39] - error:  TypeError: Cannot read property 'hasOwnProperty' of null
    at postParse (/nodebb/node_modules/nodebb-plugin-markdown/index.js:181:15)
    at /nodebb/node_modules/async/dist/async.js:66:19
    at nextTask (/nodebb/node_modules/async/dist/async.js:5310:14)
    at next (/nodebb/node_modules/async/dist/async.js:5317:9)
    at /nodebb/node_modules/async/dist/async.js:958:16
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
2018-04-07T11:10:49.160Z [39] - info: [app] Web server closed to connections.
2018-04-07T11:10:49.169Z [39] - info: [app] Database connection closed.
2018-04-07T11:10:49.170Z [39] - info: [app] Shutdown complete.
[cluster] Child Process (39) has exited (code: 1, signal: null)
[cluster] Spinning up another process...

followed with 3 restarts in 10 seconds, most likely an error on startup. Halting.

I was crating bug to GitHub, but thought that this could be know issue, after upgrade, so thats why added this question first... I did se you managed to do it fist, so I added information to there. I use tags, both 1.4.5 and 1.4.6 has this issue.

https://github.com/NodeBB/NodeBB/issues/5631

I have setup, where config.json has following entry:

{
  "url": "http://localhost:4567/forum",
}

Old images upgraded from 1.0.3 version are working fine shows example: /forum/uploads/profile/92-profilecover, but when uploading new image it tries to load them from /assets/uploads/profile/1-profilecover.jpeg, so /forum prefix is totally missing, if I remove /forum from config.json new pictures are working, but old pictures do not.

Changing /forum to /forum1 both old are new are broken.

So relative part of url is in metadata... and it is not added using new version. Also it can't be changed later?

So I'n my opinion it is bug that it ignores categories for some people. How to delete those entries in MongoDB?

All the categories where ignored for that person, but they where not before, (at least not all), was there some kind of change regarding this?

Is there way to un-ignore to all? Then there could be post telling to people to ignore again if needed.

As that was so "easy", any clue why history of private chat messages is not showing for some users? (for this user it does show up )

Hello,

Last week I updated one incase from 1.0.3 to 1.4.5, first test instance using dump and then live instance. I did ran upgrade for scheme, using versions 1.1.2, 1.2.1, 1.3.0, 1.4.5 and now with 1.4.6 (last one only in test using old dump).

Everything seemed working fine, otherwise I wouldn't have upgraded live version, but some users have reported when logged in Home Page that is routing to recent is empty, and after doing some tests I noticed that also unread route is also empty for that person.

Some other have reported that there is also history of private messages missing, that I haven't confirmed and that is reported only in live (using 1.4.5)

Site uses MongoDB (3.4.3) and live site is behind Nginx, but test version does not use that.