1.5.0 Breaking Changes

[baris]

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

If you have any plugins using any of those hooks, please upgrade your plugin and add

"nbbpm": {
   "compatibility": "^1.5.0"
}

to your package.json.

Apart from the hook parameter changes we have a bunch of other breaking changes in 1.5.0. Here is a list of them and the relevant changes in themes & plugins.

• upgrade async to 2.x+. This dependency has been updated, if your plugin directly uses the core module update your plugin so it uses async directly and take a look at the breaking changes for async.
• ability to filter notifications by type The /notifications page now allows notifications to be filtered by type. The core themes templates are updated to reflect this change. If you have a custom theme apply these changes.
• change topics.getUnreadTopics and topics.getUnreadTids to accept params object. These two methods accept an object as parameters know, any plugin that uses these methods needs to be updated to the new signature.
• add caller uid to User.updateProfile and filter:user.updateProfile, action:user.updateProfile. The first param to this method is now the uid of the user making the call. The uid of the user being updated is in data.uid.
• filter:widget.render returns string If you have a widget hook it should pass back the data it receives as a parameter instead of sending back a string. The old way will still work but it is deprecated and will be removed in a future release. See this for the updates.
• Need Requester UID In 'filter:post.get' Hook The parameters from filter:post.get changed to pass in the uid of the user. There is a new hook called filter:post.getPostData which only has the post data.

[julian]

As of v1.4.4 nconf.get('upload_path'); is no longer a relative path pointing to the uploas directory, it is now an absolute path to the uploads directory. Change introduced in commit aaacdb8413c9bc3f3d47c249c0d0287eac1cad88