Community

1.8.0 Breaking Changes

NodeBB Development

Suggested Topics

  • barisB

    1.12.0 Breaking Changes

    NodeBB Development
    2 Votes
    2 Posts
    1441 Views
    barisB

    Theme Breaking Change

    Category watch state by barisusakli · Pull Request #7109 · NodeBB/NodeBB

    Add a new not-watching state to categories. Add ACP setting to set the default watch state for all users Add UCP setting to override the ACP setting Remove cid::ignorers, replaced by cid::uid:watch:state. The score is the user's watch state (1-ignoring, 2-notwatching, 3-watching) Upgrade script to set ignoring state if user was in cid::ignorers

    favicon

    GitHub (github.com)

  • barisB

    1.9.0 Breaking Changes

    NodeBB Development
    0 Votes
    1 Posts
    1385 Views
    barisB

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

    Issues · NodeBB/NodeBB

    Node.js based forum software built for the modern web - Issues · NodeBB/NodeBB

    favicon

    GitHub (github.com)
    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.

  • jongarrisonJ

    Plans to update jQuery in NodeBB? (Currently uses 1.10.2)

    NodeBB Development
    0 Votes
    9 Posts
    2703 Views
    jongarrisonJ

    @pichalite Very cool! Thanks!

  • barisB

    filter:<template>.build changes

    NodeBB Development
    5 Votes
    1 Posts
    1468 Views
    barisB

    Related issue

    Unify build hooks? · Issue #4587 · NodeBB/NodeBB

    The same format is being used for 90% of the build hooks, yet no build hook exists for many routes. By modifying a few anomalies, I think the same function could be called in the render middleware for every route's build hook. Which woul...

    favicon

    GitHub (github.com)

    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.

  • barisB

    0.7.0 Breaking Changes

    NodeBB Development
    4 Votes
    13 Posts
    7124 Views
    psychobunnyP

    I want to escape by default, to prevent accidental XSS. If you intentionally want to allow scripts then you should use double curly brackets

    I think its something I would rather break today than worry about it in future

Copyright © 2023 NodeBB | Contributors