Now, as for why the email entry is in an interstitial, I think that is mostly an aesthetic decision. There may have been other considerations, but I cannot recall them right now.
I think a registration page should be slim by design, asking only the required questions to proceed.
After that, the interstitial page would ask all optional questions (unless otherwise configured). Email can be skipped, although TOS and GDPR questions need to be checked.
@magnusvhendin Hey there, sorry about the delay, I've been on vacation the past couple of days.
The reason the email was made optional is because not all sites require email, and even if they did, any semi-determined individual would just put in random garbage.
There were two issues with this:
With this change, an email must be confirmed before it is associated with the user account. This allows the forum admin to be absolutely certain that the email is genuine. Otherwise the user just has no email address, which is perfectly ok too.
@onur-baran You'll want to share the server side error. Just saying it's a 502 doesn't help us debug
@crazycells functionality wise the form is made required though, yes? Just the labeling is wrong?
Sounds like a bug, file on GitHub please 
A very good suggestion, we should definitely strive for colourblindfriendliness (is that a word?)
Can you open an issue against the main GitHub repo?
@crazycells Thanks for the reminder, it's an easy fix, just haven't had time to do it yet.
@pyc4 can you provide the CSV header (the first line, basically)?
We can probably write a user script to do this quickly.
@volanar contact us at [email protected] and we can discuss details
@subesh-s Have you tried using the login utilities route in the write API? It should send back a valid session cookie.
@raj-0 Can you show me an example of the call you are making, using curl? That would be the easiest way for me to debug
@sinisterspatula Probably, yes.
The thing is, we don't interface with MongoDB directly. We use an abstraction layer, and so if your database of choice supports all of the commands we throw at it (you can see the abstraction layer methods in src/database/*), then NodeBB can theoretically support it.
@magnusvhendin Thanks for contributing!
Yes, that particular test will fail if you add a language key to en-GB. What usually happens is when the PR gets merged, nodebb-misty picks it up, and automatically commits the fallback strings.
So of course this doesn't happen in pull requests 
For now, you can comment out the last it() block in tests/i18n.js, and check that tests pass. If they do, then open the PR, we'll still merge if the i18n test fails 
@frankm I believe this is fixed in master
It's specifically an issue with Node v16... downgrading to v14 should fix the issue for now.
@frankm That error shouldn't crash NodeBB. What do you mean when you say "nothing happens"?
Hi @frankm -- thanks for reporting... regarding the error message: "were the same" or not the same?
This is significant because id and credId are supposed to be the same 
@yLothar helped me work through an issue where they were not the same, and that was fixed in v3.0.3 of the plugin.
Edit: I took a closer look at your post, and you are using the funky (not in a good way) v3.0.2 version. Please upgrade to v3.0.4
@tobiasdossinger The real question here is why you need javascript enabled...
I am 95% certain you came here because maybe a theme of yours you have suddenly stopped working, with a cryptic error about turning javascriptEnabled on, yes?
In that case, you may want to audit your theme and figure out what exactly needs javascript in your LESS... there really is no reason to that I have come across... although I could be mistaken.
In Persona's case, it was the .opacity() mixin, which was not required anymore, as opacity is well supported cross-browser now: https://github.com/NodeBB/nodebb-theme-persona/commit/e14d38b827591c9681a5fcd43ca4b206297eaff5
Ever since the very first commits to the NodeBB codebase, we’ve made it a point of pride to implement features and functionality that “no other forum has”. We wanted to set ourselves apart from other community software offerings by natively supporting new UX paradigms (e.g. single page app, markdown editor, or infinite scrolling), or supporting the latest technologies (e.g. external SSO login, RESTful API) endemic1 to popular web applications.
Today, I am happy to announce that NodeBB officially supports Multi-factor authentication via hardware keys. This functionality was recently added to v3.0 of the Two-Factor Authentication plugin for NodeBB. The plugin already supported a second factor via a time-based one-time password (TOTP), and further support for hardware keys allows users to increase security even more so.
Support for hardware keys via the WebAuthn protocol was sponsored by @yLothar and the mechanical keyboarding community at keeb.it. Thank you!
[…]
Click here to see the full blog post
