@girish there may be something wrong with your dns. I can access that link just fine.

Tags allow % character now, themes will need to be updated to use tags.valueEncoded instead of tags.valueEscaped https://github.com/NodeBB/NodeBB/issues/10135 See changes in persona to update your custom theme https://github.com/NodeBB/nodebb-theme-persona/commit/6aada9127865ddc1cbaf8cd5f548ebc78f7bf90a

plugins.registerHook removed, use plugins.hooks.register plugins.unregisterHook removed, use plugins.hooks.unregister plugins.fireHook removed, use plugins.hooks.fire plugins.hasListeners removed, used plugins.hooks.hasListeners https://github.com/NodeBB/NodeBB/commit/dd4e66e22c93586d389b47fa197154620508ae8f#diff-b4eb852db38c86236f6d2c1b7fcfc03c1b93a090a534361b9c21e790620fce39

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

We have received reports that after upgrading to v1.16.0, the amount of websocket connections is very high relative to pre-upgrade This is due to older socket.io clients (running on version 2) attempting to connect to the new socket.io 3. These protocols are incompatible, and so the connection is rejected, and NodeBB was configured to try indefinitely. This is ok. Over time, as your users close their browser windows (or refresh), they will automatically start using the latest version, and socket usage will return to normal levels. If you are worried about the excessive traffic, you can configure a nginx condition to drop requests with the query string ?EIO=3. Please see the issue linked above for more information.

@baris Thanks, that was this ! This problem is solved now.

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

Apparently the Calendar Plugin: nodebb-plugin-calendar Calendar and events for NodeBB Installed 1.0.0-alpha.50 | Latest 1.0.0-alpha.50 Does not work with 1.13.0 Can someone please update it?

Theme Breaking Change https://github.com/NodeBB/NodeBB/pull/7109

@faizanzahid the current version of NodeBB still has compatibility with those plugins. Future version will not.

Hi, I think I have discovered another breaking change that you didn't mention, though it is probably super-niche. This commit: https://github.com/NodeBB/NodeBB/commit/ec91ef1c644044bba44198b031913655e784b4bb broke our custom SSO plugin. The result was that after successfully logging in our external identity provider and being redirected to our Forum's callback endpoint, I was ending up not logged in (the button in the header still said "Log in") and stuck on /register/complete roadblock. It looked like our Passport strategy verify callback, that parses output from the identity provider and fetches user data via OAuth2 was not invoked at all. It turns out that the changes in this commit don't play well together with passport-oauth2 (https://github.com/jaredhanson/passport-oauth2) internal ability to protect against CSRF (which we were using). This strategy was already using state parameter to pass its own CSRF token. I don't have more time to investigate but I suspect things shipwrecked when NodeBB overwrote the state parameter with its own CSRF token. Turning off passport-oauth2 internal CSRF protection (by removing state: true from its options) fixed the issue.

Please see the following issues for breaking changes to plugins and themes. https://github.com/NodeBB/NodeBB/issues?utf8=✓&q=is%3Aissue+milestone%3A1.9.0+label%3A"breaking+change+(themes)"+ https://github.com/NodeBB/NodeBB/issues?q=is%3Aissue+milestone%3A1.9.0+label%3A"breaking+change+(plugins)" If you have plugins that are affected, please update your plugin and add the below to your package.json "nbbpm": { "compatibility": "^1.9.0" } to your package.json.

@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.

Due to changes introduced to loading javascript assets in 1.7.0, using jquery in widgets requires waiting for the page load event. Sample widget for 1.7.0+ if (window.jQuery) { doStuffThatUsesJquery(); } else { window.addEventListener('load', doStuffThatUsesJquery); }

Just an update to those following this post, that NodeBB v1.6.0 has entered the feature freeze portion of the launch as of 31st of August 2017 Code Freeze is schedued for this Thursday (7th of September), with a launch a week later, on the 14th of September.

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

Please see https://github.com/NodeBB/NodeBB/pull/4662 If you have a custom theme that has a partials/topic/watch.tpl you will need to update it for 1.1.0. You can see the changes you need to make in https://github.com/NodeBB/nodebb-theme-persona/pull/278/files Persona, vanilla and lavender themes are already updated.

Related issue https://github.com/NodeBB/NodeBB/issues/4587 As discussed in the issue, we had a bunch of hooks to modify a page on some routes like filter:recent.build. These were added as required but most pages didn't have a hook so if you needed one you would have to ask us to add it and wait for the next release. With the above change every route has a hook. The hook name is derived from the template name passed to the res.render(template, data); method. For example if your template is named myAwesomePage, you render it with res.render('myAwesomePage', data); and the hook that will be fired is filter:myAwesomePage.build Every hook gets 3 parameters {req: req, res: res, templateData: data}, data is the parameter you pass into the res.render method. We had a few inconsistencies in the parameters passed to the hook and the hook name below are the changes that needs to be fixed if you have a plugin that is listening to these hooks. filter:groups.build is now called filter:group/details.build as that is the correct name for that template. filter:popular.build used to pass in a extra term parameter, this moved into the templateData parameter. filter:header.build this is removed it was deprecated a while ago. Use filter:navigation.available instead. filter:search.build parameters changed, data is no longer passed in use req.query and req.params instead. results is now the templateData parameter. Feel free to ask any questions if anything isn't clear.

But... It's a breaking change. You should not do such stuff when you have now 1.0

[image: qNpD24R.png] No announcement thread in the announcements section? Congratulations, guys! NodeBB has come a long way.