Buy Hosting

Gotchas for 0.3.0

NodeBB Development

Suggested Topics

  • barisB

    NodeBB 3.2.0

    NodeBB Development
    7 Votes
    8 Posts
    305 Views
    omegaO

    @baris All good, after I ran some system updates, then did another build and this time, no error!

  • julianJ

    NodeBB v3.0.0-rc.1 β€” The release candidate

    NodeBB Development
    11 Votes
    6 Posts
    455 Views
    FrankMF

    @DownPW said in NodeBB v3.0.0-rc.1 β€” The release candidate:

    ./nodebb stop
    git fetch && git checkout develop && git reset --hard origin/develop
    ./nodebb upgrade
    ./nodebb start

    Thanks. My test forum is now on v3.0.0-rc.1.

    @julian @baris Thanks for v3 πŸ€“

  • psychobunnyP

    NodeBB 1.12.0: keeping warm with email, search and spam fighting improvements

    Moved NodeBB Development
    9 Votes
    4 Posts
    991 Views
    scottalanmillerS

    Three sites updated thus far, no issues.

  • barisB

    1.10.0 Breaking Changes

    NodeBB Development
    1 Votes
    3 Posts
    2k Views
    attisA

    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.

  • alff0x1fA

    Nodebb v1.3.0

    NodeBB Development
    3 Votes
    1 Posts
    1k Views
    alff0x1fA

    NodeBB team release v1.3.0.

    Thats new:

    Add to post "replies to this post" link (expands/collapses the replies inline under the post) SSO plugins can to redirect users back to the page they were on User is able to restore deleted posts EU Cookies Notification/Warning Show original post/topic etc dates older than month (customizable) add registration queue approvals/rejections to the event log fix collision of button text in user picture changer on mobile/tablet devices refactor favourites (favourites become bookmarks) breaking change plugins and themes edit password screen can display validations default group chat name to usernames automatically deleting the topic with no posts (when moderator delete last undeleted post) allow regular moderators to access the general flagging interface textcomplete update to 1.7.2

    Мore: https://github.com/NodeBB/NodeBB/milestone/48?closed=1

Copyright Β© 2023 NodeBB | Contributors