Skip to content

Technical Support

Need help with installing or configuring NodeBB? Look here.

4.8k Topics 26.5k Posts

Subcategories


  • User documentation for NodeBB

    44 Topics
    44 Posts
    Jay MoonahJ
    One of the first important things to do after setting up NodeBB is to set up an emailer plugin. While NodeBB does include a local emailer, if your forum is particularly active we recommend using an third-party emailer such as SendGrid which provides better deliverability for sites that send a high volume of email. Setting up SendGrid in NodeBB is very easy. Open the administrative dashboard using the 'gear' icon on your forum. Open the Extend > Plugins menu, and select the Find Plugins tab. Use the search on the right. Type 'SendGrid' and the plugin should appear -- select Install when you see it. From Installed tab on the Plugins menu, search again for 'SendGrid' and select Activate. Activating the plugin will require a restart of your forum. To restart, select the Dashboard menu and press the Restart button to the right. After NodeBB restarts, the SendGrid plugin will be active. After you restart, there should be a item called Emailer (SendGrid) under the Plugins menu -- if you don't see this right away, try refreshing your browser. Sign up to SendGrid Go to the SendGrid website, open the pricing page and scroll to the bottom. Click on the link and create your free account. Once you've confirmed your SendGrid account via email, you should be able to login to the SendGrid website. On the left side of your SendGrid dashboard, open Settings and click on API Keys. Click the button in the top right to create a new key. Make sure that the key has Full Access for Send Mail and Alerts.  When you are done, the new key to your clipboard. Now, return to the SendGrid menu on your NodeBB admin panel. Paste the API key into the field, and save your changes. Now go back to the Dashboard to restart your forum one more time. SendGrid should now be working for your forum. [image: youtubelogo.png] Setting up SendGrid mailer for NodeBB
  • NodeBB guides, how-to's and general tips and tricks

    83 Topics
    601 Posts
    Z
    not sure the plugin worked for firefox. saw a-z in the sort icon. when i used it, i expected the topics in the category would be sorted a-z. they werent
  • 25 Topics
    201 Posts
    eeeeeE
    I think you answered my point, by agreeing there are issues. I didn't even attempt to deploy nodebb, I had problems with much smaller projects! Nextjs routing was going through a change of design at the time, so perhaps that is less confusing now, but there were multiple other headaches. I would get build errors and issues with package management.
  • All users' status is invisible

    Solved
    14
    0 Votes
    14 Posts
    2k Views
    murcsM
    @baris said in All users' status is invisible: The script @pitaj posted will set lastonline field of the user to Date.now if you don't want that remove it from the data object above. unfortunately we had to remove the other lastonline line(s) in setUsersOnline()too. function setUsersOnline(callback) { var batch = require('./src/batch'); batch.processSortedSet('users:joindate', function (uids, next) { // const lastonline = Date.now(); const data = { // lastonline, status: 'online', }; async.parallel([ cb => async.each(uids, (uid, next) => { db.setObject(`user:${uid}`, data, next); }, cb), // cb => db.sortedSetAdd('users:online', uids.map(() => lastonline), uids, cb), ], next); }, callback); } no idea why lastonline is manipulated by the script anyway.  to force a re-login to see it taking effect the forum was rebuild and restarted after running the script.
  • Breaking change for plugins

    Solved
    7
    0 Votes
    7 Posts
    749 Views
    D
    Somehow it was uninstalled. Weird. There was also a bug in the code. Maybe a node.js version issue.
  • Custom Home page

    2
    0 Votes
    2 Posts
    409 Views
    barisB
    https://github.com/NodeBB/NodeBB/pull/9180
  • Couldn't set default admin username and password in config.json

    12
    0 Votes
    12 Posts
    2k Views
    PitaJP
    @venkat what was the output of that command? NodeBB starts up fine?
  • A few questions about NodeBB

    3
    0 Votes
    3 Posts
    451 Views
    Wocek DerejczykW
    @Julian Thanks for your help.
  • Manually change digest settings

    Unsolved
    2
    0 Votes
    2 Posts
    377 Views
    PitaJP
    I think a script like this could work: 'use strict'; var nconf = require('nconf'); var async = require('async'); nconf.file({ file: 'config.json', }); nconf.defaults({ base_dir: __dirname, views_dir: './build/public/templates', }); var db = require('./src/database'); async.series([ db.init, process, ], (err) => { if (err) { console.error(err); process.exit(1); } process.exit(); }); const freq = 'off'; // or daily, weekly, monthly function process(callback) { var batch = require('./src/batch'); var User = require('./src/user'); batch.processSortedSet('users:joindate', function (uids, next) { async.parallel([ cb => async.each(uids, (uid, next) => { User.setSetting(uid, 'dailyDigestFreq', freq, next); }, cb), cb => async.each(uids, (uid, next) => { User.updateDigestSetting(uid, freq, next); }, cb), ], next); }, callback); } I think this should work to set all users to a specific frequency. Please backup your database before trying this. You might also need to fix a couple JS errors, I haven't tried this myself. Create a new file called process-users.js in your main nodebb directory (the one with config.json etc), paste that script into it, set the frequency you desire, and run node process-users from within that directory to set all of your users to the selected frequency.
  • a picture only category? (like instagram)

    2
    0 Votes
    2 Posts
    374 Views
    data-dataninjaD
    [image: 1609879032105-screen-shot-2021-01-05-at-8.32.19-pm-resized.png]
  • This topic is deleted!

    Locked Solved
    4
    0 Votes
    4 Posts
    16 Views
  • Favicon reset to NodeBB after upgrade

    Solved
    6
    0 Votes
    6 Posts
    752 Views
    barisB
    It could also be due to the tinycon dependency see here
  • Make uploaded files private...?

    13
    0 Votes
    13 Posts
    3k Views
    gotwfG
    @crazycells Nope. Not unless you feel the urge/need. I was making more of a generic comment pointing out a potential pitfall. Cuz there's always a sub population of miscreants who will try to exploit the hard work of others for jollies, profit, etc.
  • Which is the nodebb community theme

    8
    0 Votes
    8 Posts
    893 Views
    oplik0O
    You can actually use NPM to install from a specific branch of a GitHub repo. Just do npm install NodeBB/nodebb-theme-persona#timeline-style Right now the version in package.js on this branch is the same as on the main branch (10.3.16) so it should work without any changes to NodeBB package.json (not sure if the version of installed theme is checked at the startup, but with the same version it doesn't matter) Edit: but as Julian said it's work in progress and, so it may be buggy. Also, I'm not sure if NPM will update it from its registry automatically on your next nodebb upgrade or if you'll have to manually install it back.
  • Use response:router.page instead of filter:router.page (deprecated)

    5
    0 Votes
    5 Posts
    551 Views
    A
    @julian Yes. I saw it. Thanks !
  • TreeError on build

    9
    0 Votes
    9 Posts
    877 Views
    A
    @pitaj I made two issues on benchpressjs related to this topic if it helps : https://github.com/benchpressjs/benchpressjs/issues/98 https://github.com/benchpressjs/benchpressjs/issues/99
  • snowing theme

    5
    0 Votes
    5 Posts
    645 Views
    murcsM
    @oplik0 said in snowing theme: <script src="https://cdn.jsdelivr.net/gh/nextapps-de/snowflake@master/snowflake.min.js"></script> try it in combination with nodebb-plugin-night-mode!  it becomes a heartwarming winter dream.
  • Rename some functions using plugin?

    3
    0 Votes
    3 Posts
    423 Views
    N
    @pitaj Thank you very much!
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    5 Views
  • 0 Votes
    2 Posts
    4k Views
    PitaJP
    @varun-ganesh-d that means that for at least one the unverified users, they provided an email that doesn't exist.
  • Getting logged in user token

    6
    0 Votes
    6 Posts
    946 Views
    julianJ
    @vinu Ah, you'll want to pass an actual uid into the _uid query parameter, not a user token. I think that's the issue here.
  • Permition for Cross domain access

    11
    0 Votes
    11 Posts
    997 Views
    julianJ
    @mahidul-moon good question, it is because Postman automatically sends the browser cookie if it detects one It's actually really annoying how postman does that...
  • Unable to edit large post - request entity too large

    5
    0 Votes
    5 Posts
    694 Views
    julianJ
    @baris is correct, it is an error thrown by express because the large post is larger than the system default. See http://expressjs.com/en/resources/middleware/body-parser.html#bodyparserjsonoptions In NodeBB, we assume the default provided by body-parser, which is 100kb If you want to support longer posts, update this value by adding this to your config.json { ... "bodyParser": { "json": { "limit": "1mb" } } I take no responsibility for whether these values actually work, but I think they should