Admin > (SETTINGS) User > Default User Settings [image: RoO3t8a.png]

Prioritizing SSO seems to make a lot of sense. Simplifies and speeds up authentication and encourages user registration by replacing typing in email/password with simple click/tap and accept. [image: 7F3ehjZ.jpg] It would be nice to have a switch to reverse Email/SSO priority and a link to reveal (unhide) email registration. There is a solution pointed out by @PitaJ but using CSS will not allow auto-translation and may be uncomfortable for some.

Long usernames are generated when using SSO at registration (all good).

@h7 Thanks, this helped, in my case with no need to make the app public. It's still "In Development", but working. The settings at Facebook for Developers are like the following: Settings > Basic Display Name: Example Community Login App Domains: example.com Contact Email: [email protected] Privacy Policy URL: https://example.com/privacy/ Category: Some category Site URL: https://example.com/community/ Facebook Login > Settings [yes] Client OAuth Login [yes] Web OAuth Login [no] Force Web OAuth Reauthentication [yes] Use Strict Mode for Redirect URIs [yes] Enforce HTTPS [no] Embedded Browser OAuth Login Valid OAuth Redirect URIs: https://example.com/community/auth/facebook/callback [no] Login from Devices Well, not sure if all this is needed, but after many tests it's working this way. There is also the interesting video Facebook SSO for NodeBB - YouTube, which is helpful although not complete.

@pitaj short and clean solution, thank you! How about rewriting the title? Here is the custom CSS but I guess this will not get translated to Chinese for e.g.: @media(max-width: 992px) { .page-login #content .row { display: flex; flex-direction: column-reverse; } .alt-login-block h4 { visibility: hidden; } .alt-login-block h4:after { position: absolute; padding: 0px; top: 0px; display: block; visibility: visible; content:'Social Login'; } }

@julian Thank you!

@baris

Hey @Julian Maybe you could post the config on the README.md of the github project. It will be more effective. Only a suggestion. Thanks for the plugin.

I am trying to do the same thing. I change the timestamp in mongoDB, but it has no effect on the frontend. Ps.: I changed the timestamp on topic, post and topics:recent. Anyone can help me?

@h7 tried on a different Debian 7 (Wheezy) server, to make sure this is a common issue: Node.js v4.2.2 Redis server v=3.2.11 NodeBB v1.0.3 NodeBB installs again, without errors but the log comes back with the exact same [2458] - error: undefined npm rm nodebb-plugin-emoji-one npm install [email protected] fixed that error, now: info: Time: Sun Oct 08 2017 04:59:32 GMT+0300 (MSK) info: Initializing NodeBB v1.0.3 [outdated] nodebb-plugin-emoji-one installed v1.1.4, package.json requires 1.1.0 warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them: warn: ./nodebb upgrade [cluster] Child Process (6503) has exited (code: 0, signal: null) OK, removing the plugin npm rm nodebb-plugin-emoji-one and ./nodebb start worked, NodeBB v1.0.3 running, still can't log-in: warn: [meta/dependencies] Bundled plugin nodebb-plugin-emoji-one not found, skipping dependency check. [minifier] file not found, node_modules/socket.io-client/socket.io.js [minifier] file not found, node_modules/socket.io-client/socket.io.js info: NodeBB Ready info: Enabling 'trust proxy' info: NodeBB is now listening on: 0.0.0.0:4567 error: /login invalid csrf token error: /login invalid csrf token using older versions of socket.io: npm remove socket.io npm remove socket.io-client npm install [email protected] npm install [email protected] did the trick, NodeBB v1.0.3 running and ready for myBB to NodeBB transition

pkill -9 node then ./nodebb restart and service nginx restart fixed all problems. It seems a previous NodeBB was still running in memory @PitaJ thans a lot for the help! Truly amazing app with excellent community support!

When re-run ./nodebb setup, it did ask for the admin user/password (before it was an existing db present) so it's working now, thank you! In case someone would miss that or forget the admin pwd, what's the solution (via redis)? I saw a post somewhere but can't find it any more.