Introducing the NodeBB 0.7.0 Persona preview

Moved NodeBB Development

Suggested Topics

  • 7 Votes
    14 Posts

    We haven't released a new RC but there are some small fixes in harmony and core since the last rc. If you want to grab those you can update core and run upgrade. On develop branch.

    ./nodebb stop git pull ./nodebb upgrade ./nodebb start
  • 3 Votes
    6 Posts

    ๐Ÿค” interesting...

  • 0 Votes
    3 Posts

    Also, I added a link to it in the nav bar as well

  • Is NodeBB still free?

    Solved NodeBB Development
    0 Votes
    6 Posts

    @julian said:

    That's not a bad idea... we just don't have plans to split the sites yet.

    I understand that you don't want to split up anything, but how about mentioning the OpenSource version at all? ๐Ÿ™‚
    Right now, when I go to, the only chance to see that there is a free version that I can roll out myself is to know what the github logo looks like and then scroll down all the way to the bottom to spot it there (very small, barely visible).
    Additionally, if I have AdBlock Plus turned on, these social buttons do not appear at all.

    I perfectly understand that you want to earn money and therefore want to focus the page around your hosting service but I think that you could significantly cut the amount of requests from people who heard about a cool OpenSource forum and who now struggle to find a link to download it.

  • Gotchas for 0.6.0

    NodeBB Development
    0 Votes
    1 Posts

    I know I made a promise to have the 0.5.x branch last more than 2 releases, but we added more breaking changes again, and 0.5.0 hasn't even been released yet ๐Ÿ˜†

    In any case, for those plugin developers who are interested:

    Notification pushed action hook (action:notification.pushed) incoming data has changed: From: An object containing the notification data To: This object -- {notification: notification, uids: uids});

    As always, this list will be updated as new breaking changes are added. In the case of this list -- don't commit and publish your change to npm yet, as 0.6.0 has not launched. We recommend you maintain these changes in a separate branch until then.