It's not news to say 2020 has been... challenging. In Toronto, the home of NodeBB HQ, we've gone from a spring lockdown to a cautious summer reopening, to lockdown again — sigh. But the team has never stopped working, and have managed to squeeze out one last release before we thankfully turn over the calendar.
I already reported this on github - this is just for the information of other users:
There seems to be a bug in saving group information. I noticed it, when trying to display some badges for certain groups. I faced the situation on
NodeBB version: 1.16.1
Steps to reproduce are:
- Admin->Manage->Groups ->click'Show Badge'
- Saving information 'Success Changes saved!' is displayed
- Leave Page ->'You have unsaved changes. Are you sure you wish to navigate away?' is displayed
- Re-check resent changes: Changes not saved for checkboxes: 'Show Badge', 'Private', 'Disable join requests', 'Disallow users from leaving the group', 'Hidden'
The HTTP response code for one type of rejected response has changed
If the system is configured to allow login via "username only" or "email only", and you attempt to log in with an incorrect login type (i.e. username instead of email, or vice versa), a HTTP 400 will be sent back instead of HTTP 500
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.
As far as I understood most of the discussion is made there. Furthermore I understood that the GDPR plugin was made for migrating old forums to the new consent mostly required by EU regulations in May 2018. So my problem in 2021 is:
I would like to ask all our users to consent once again AND to change the sources they are consenting to. I thought the gdpr plugin might be helpful - but as far as I understand I am not capable to unset the consent state with it. So basically my questions are two:
how do I unset the consent state of (all) users?
are they forced to consent for the next login?
NodeBB tests require database setup beforehand.
I recommend just checking out how NodeBB currently does it with GitHub Actions or how it was done earlier with TravisCI
I haven't used GitLab CI much, but I think the services part is pretty similar to GitHub Actions - there are some setup differences (per job variables instead of per service env for example), but I think just adapting the service configuration to GitLab syntax will be better than the bash based install from TravisCI
We are looking to hire someone to do some custom theme work with either the persona or material theme for one of our clients. Please email me sterling [at] luceosports [dot] com with the subject 'NodeBB Development' if interested.