1.8.0 Breaking Changes

[baris]

Please see the following issues for breaking changes to plugins and themes.

https://github.com/NodeBB/NodeBB/issues?q=is%3Aissue+label%3A"breaking+change+(plugins)"+milestone%3A1.8.0+is%3Aclosed
https://github.com/NodeBB/NodeBB/issues?q=is%3Aissue+milestone%3A1.8.0+label%3A"breaking+change+(themes)"+is%3Aclosed

If you have plugins that are affected, please update your plugin and add the below to your package.json

"nbbpm": {
   "compatibility": "^1.8.0"
}

to your package.json.

[baris]

To implement spiders as a system group we are making a breaking change in 1.8.0. If you are using req.uid to determine if a user was logged in or not in your plugins you need to change it to req.loggedIn. req.uid used to work because logged in users always had a positive uid and guests had a uid of 0. With 1.8.0 spiders will have a uid of -1 so we added a loggedIn property on the request object.

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

[baris]

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

[julian]

Hello all,

The community forum (you're on it!) has been updated to the latest master, which contains release-candidate code for v1.8.0. Please let us know if you notice any regressions.

The scheduled launch for v1.8.0 is 14 March 2018

Thanks!

[Jenkler]

Nice work Will do!

[jw.sbat]

Hi folks, congratulations with the release. I am looking forward to install it. Should I run this on a staging environment? How do I know if the plugins are working, is there a whitelist somewhere? I am using question-and-answer but it doesn't have the compatibility flag in package.json.

[baris]

@jw-sbat Always make sure the plugins you are using are working fine before deploying to production. Even if the plugin doesn't specify compatibility directly it could still work. That property specifies a minimum nodebb version.