Skip to content

Technical Support

Need help with installing or configuring NodeBB? Look here.

4.8k Topics 26.7k 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.
  • 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
    835 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
    991 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
    639 Views
    A
    @julian Yes. I saw it. Thanks !
  • TreeError on build

    9
    0 Votes
    9 Posts
    977 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
    730 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
    485 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
    1k 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
    1k 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
    772 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
  • Can't Register as New User

    Solved
    6
    0 Votes
    6 Posts
    742 Views
    julianJ
    @waugh I've marked it solved for you you can do so from the topic tools menu
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
  • 0 Votes
    7 Posts
    2k Views
    N
    @pitaj No sorry, that didn't solve. But following worked: After importing mybb, upgrade it to v1.16.0 which produces "Error: ENOENT: no such file or directory, open '/nodebb/node_modules/nodebb-plugin-require/plugin.json' " as mentioned above. Back up both database and any image files imported from mybb under public/uploads/files Delete whole nodebb files and database Install original v1.16.0 (git clone -b v1.16.x https://github.com/NodeBB/NodeBB.git) Remove only the database, then restore database and image files using backups Works well, it doesn't produce any error even after installing quickstart plugin. Additionally, https://github.com/NodeBB/nodebb-plugin-quickstart doesn't work on v1.16.0. It shows following error on Chrome and the page got frozen while loading: colorpicker.js:11 Uncaught TypeError: n.ColorPicker is not a function at HTMLInputElement.<anonymous> (colorpicker.js:11) at Function.each (jquery.js:381) at C.fn.init.each (jquery.js:203) at Object.n.enable (colorpicker.js:8) at o (admin.js:31) at Object.i.init (admin.js:9) at ajaxify.js:336 at Object.execCb (require.js:1696) at n.check (require.js:883) at n.<anonymous> (require.js:1139) Anyways, it's not to be discussed here I guess. Thank you very much!
  • Remove post revision from edit history as a moderator/admin

    3
    0 Votes
    3 Posts
    395 Views
    julianJ
    @cryptoethic As @pitaj has said, this is in our backlog, so it is not available at present. If you need a solution immediately, you can scrub the entire edit history for that post. Delete the key post:<pid>:diffs and all keys that start with diff:<pid> e.g. redis-cli keys diff:123.* | xargs redis-cli DEL
  • Errors when updating from latest 1.15 to 1.16

    10
    0 Votes
    10 Posts
    919 Views
    tecyT
    Hi, there was a problem with old plugins. For the future I wold suggest to list all active used plugins. Then disabling all of them and the update the forum. If eveything is ok, update the plugins step by step to see if something goes wrong. @PitaJ Thanks for yopur help. In the future I have to read the error messages more carefully. The "bad" plugins were mentioned there
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    13 Views
  • Cannot login properly after forum update

    2
    0 Votes
    2 Posts
    389 Views
    AlekseiA
    Ok, the problem was solved. But I'm not sure how exactly. After I wrote this post I noticed that the latest version of NodeBB is 1.16.x. But while upgrading the forum i switched to 1.15.x branch (I thought that was the latest). After that, I used ./nodebb upgrade command. Maybe this was the issue? Maybe, I switched to the previous version branch, but installed the latest version of files with the "upgrade" command? — I don't really know. But when I switched to 1.16.x and upgraded the forum again, then it worked as expected. The forum now works fine.