Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

When will 0.9.1 be released?

NodeBB Development

4

6

2061

Log in to reply

Fan Luo last edited by

It seems delayed. Still waiting for some of the important fix in 0.9.1... When will 0.9.1 be released?
1 Reply Last reply
Reply Quote 0
Julian Lam GNU/Linux Admin last edited by

Ask and ye shall receive

NodeBB v0.9.1 launched.
1 Reply Last reply
Reply Quote 0
J
jolly4real last edited by

How do we update?
1 Reply Last reply
Reply Quote 0
W
whitts last edited by

Whats new or fixed? Thanks
1 Reply Last reply
Reply Quote 0
Julian Lam GNU/Linux Admin last edited by

You can take a look at the closed issues here: https://github.com/NodeBB/NodeBB/issues?q=is%3Aissue+milestone%3A0.9.1+is%3Aclosed

@jolly4real I'll update your instance for you.
1 Reply Last reply
Reply Quote 0
Fan Luo @julian last edited by

@julian Thanks, I will give a try tonight!
1 Reply Last reply
Reply Quote 0

Suggested Topics

N

the custom theme will be removed
NodeBB Development • • ngo

4

0
Votes

4
Posts

85
Views

Yeah it's a known issue you'll have to relink sometimes. It depends on what npm version and OS you're using.
1.11.0 Breaking Changes
NodeBB Development • breaking 1.11.0 • • <baris>

15

0
Votes

15
Posts

1624
Views

@faizanzahid the current version of NodeBB still has compatibility with those plugins. Future version will not.
1.10.0 Breaking Changes
NodeBB Development • breaking 1.10.0 • • <baris>

3

1
Votes

3
Posts

2126
Views

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.
0 julianlam committed to NodeBB/NodeBB closes #6553
Disable one plugin? New, for v0.5.0
NodeBB Development • • Julian Lam

3

2
Votes

3
Posts

1786
Views

Haha yeah, ./nodebb reset plugin="pluginname" is already in -- would prefer a nicer syntax, so maybe we can introduce the ./nodebb disable command. Unsure atm.
?

NodeBB v0.7.0-dev
NodeBB Development • • A Former User

3

0
Votes

3
Posts

1038
Views

?

@julian said:

Right now, it's on the master branch of our GitHub repository 🙂

Yes! Thanks 🍗

| |

Copyright © 2021 NodeBB | Contributors

1 / 1