Community

Reactions Plugin for NodeBB

Plugin to add emoji reactions to posts.

0_1486754158410_upload-efabb890-bb16-4457-98c4-d03f925fa756

Installation

npm install nodebb-plugin-reactions

or

Install using ACP -> Plugins page.

Repository: https://github.com/pichalite/nodebb-plugin-reactions

Report any issues on the plugin issue tracker https://github.com/pichalite/nodebb-plugin-reactions/issues

Needs small change to theme templates for support.

Plugin is currently supported on nodebb-theme-material and nodebb-theme-slick

For demo use https://pichalite.com for material theme and http://slick.pichalite.com for slick theme.

Hi! In the search result NodeBB have title name with symbol :

I want to change it and use same like "Forum | Welcome", how to do it?

B611BCFB-8D22-4129-89AB-AFE357FE71D9.jpeg

is there any known issue with the k-key while editing in quick reply?  users at our site experience a kind of jump one or more posts up while typing the k-key.  our forum runs v2.8.4.  it happens while using firefox on windows 10 or ubuntu 20.04 on a desktop device or safari on iOS 16.3 on an iPhone or edge on windows 10 or ...  could not find any report using the search function.

Hello,

I am modifying for my personal use the nodebb-plugin-shoutbox plugin : https://github.com/NodeBB-Community/nodebb-plugin-shoutbox

I finished the French translation and I proposed it on the github.
On the other hand, the translation of the admin.json & shoutbox.json files on language directory is not enough.
You have to modify the text of other files for a complete translation.

I managed to modify the default commands and add new ones (text and sound) but there are 2 things I can't do for now, hence the creation of this topic :

Add @mention user completion :

a5707014-4912-420f-b803-6c5726dfc28b-image.png

add emojis completion :

c082f61d-5619-4573-8212-3289bdd0a772-image.png

--> If anyone could help me on these 2 topics or direct me to the right approach, I would be grateful.

Have a nice day

Should have posted this earlier but oh well, this topic quickly turned into bug report thread so please use this one to report any issues with 3.0.0.

This forum is running the latest version of core and harmony theme along with multiple plugins.

When reporting a bug please first check if it has been already reported or fixed.

3.0.0 open issues 3.0.0 closed issues

It seems to me that this is a very cool feature of the forum, if a guest sees the number of new topics (ex. only in the last 24 hr) this will create a feeling of a "live" platform, where there is activity and immediately there is a desire to join such a community.

It will also emphasize the technically peculiarity of NodeBB, guests will be able to appreciate in practice what real-time is and want to join us!

Cat Hack GIF

Please add feature to set group/category for the tags, option to set icon/color for tag and option (filter) on latest page for the view topic only with same tag.
CA522229-4DD5-4734-A2BB-27F6994A7211.jpeg
E3CB4E35-7505-464E-A235-ECE016B56D0F.jpeg

Hi everyone, new to the forum. I am looking to integrate nodeBB into WordPress somehow. Please excuse my non-tech savviness. I am a rusty web developer who is trying to set up a new business.

I would like to eventually use the website I am setting up to sell courses so looking at the MemberPress route.

I would like a single sign-on so the forum can be logged onto easily.

I have shared web hosting at the minute (Hostinger) and I don't think nodeBB can be installed on it, I was going to put the nodebb software on an Ubuntu VPS.

I hope that makes sense, is it possible and am I completely thinking about this the wrong way?

Hi,

I want to set up a development instance for testing which should be a clone of the live instance.

I could take a snapshot on DigitalOcean and create a new droplet but to do this the droplet needs to be powered off first. Is sudo shutdown -h now the right way? Any more steps to consider? I'm asking because I couldn't start nodebb last time after using the power off toggle in Digital Ocean control panel. I guess I did something like turning off a PC by switching off the power supply.

Or could I just make a copy of the nodebb folder and set up a new instance on the same droplet with a different port? Then I would use a backup of my current db? Any more steps to consider here? Is this recommended?

The forum uses MongoDB 4.2.23 and is running on Ubuntu 20.04.5 LTS.

We've been seeing a steady flow of inquiries regarding how NodeBB handles emails. I will try to head off these inquiries and at the same time, provide a central point of support for people who have questions regarding how email addresses work in NodeBB.

I'll start by stating upfront that I will divide this post into two parts — a high-level review of email handling changes, and a more technical half that details how these changes affect developers on the back end.

Secondly, I will also note that these changes have been in v1.18.0, so there is nothing new here for v3.x.

High Level Overview

NodeBB makes several assumptions:

An email is not an integral part of the user account NodeBB by default will ask you for an email, but it is optional. You can put a fake email in, or even nothing at all. However — an email is not truly associated with a user until the user has confirmed their email by clicking on the unique URL in the welcome/confirmation email. Likewise, if an account's email is changed, it is merely a request to change the email. The old email remains until the new email is confirmed. Email is not integral to the user; you can put in any email address if prompted

We wanted the flexibility of not requiring an email address for a user account.

Part of that is because validating the format of an email is tricky. If you use even a slightly obscure email, you'll have run up against issues registering on some sites that use an incomplete format check.

The second part of it is that if someone really wanted to not put their email down, they would just put something fake in, e.g. [email protected] If this happens, the best case scenario is you get emails bounced back. Worse case scenario, the fake email entered actually belongs to someone else and they mark the sender (e.g. you) as spam; which leads me to the third part.

The third part is far too many websites let users register, and allow users put in whatever email they want, even if it belongs to someone else. I refuse to allow NodeBB to become part of this unintentional spam.

The only checking we will ever do on the entered email is to make sure that it contains an @ symbol. All emails contain the @ symbol.

Aside: I have a rather common email, and I receive many emails from other people named Julian Lam, from around the world. I suppose if I ever go to Planet Fitness in the United States, I have a membership, or I can provide proof that I've ridden the bus in Cardiff, Wales. I'm also on the mailing list for a BMW dealership in Hong Kong, and haven't been able to get off of it. All the same, I'd rather not get these emails 😄

An email is not truly part of the user until it is confirmed

This is the sticking point that gets people confused — just because a user put in an email address, doesn't mean it's their email address. NodeBB will only make this assumption if explicitly instructed to (see technical overview). Otherwise, it will send out a validation email and add the email to the user account only when properly confirmed via unique code/link.

Until then, the existing email is still active, or if there is no email, then the user account continues with no email associated with that user.

Remember, the only way to ensure that an email you have is a real email... is to send it an email, and have the user physically confirm it. Full stop.

What if I want to restrict access to my content to verified users only?

We've introduced two new system groups to complement the original registered-users group. The three relevant groups now are:

registered-users — contains all users irregardless of email confirmed state verified-users — users whose email has been confirmed unverified-users — users who have no email, or whose email has not yet been confirmed

By default, a new category will allow topics and replies from the registered-users group. Remove those privileges and apply them to the verified-users group as necessary. If you want a category specifically for unconfirmed users, then apply them to the unverified-users group.

What if I know the user's email is correct, or want to add an email to a user?

If you are an administrator, editing the user's email via their profile will bypass the confirmation request and automatically validate their email. With great power comes great responsibility.

Technical Overview NodeBB no longer trusts the email property in the user hash, and hasn't since v1.18.0. it is now purely informative. email:uid is the source of truth for what email belongs to which user. When user.create is called (either via code or by API), if email is a passed-in property, then NodeBB will try to send a confirmation email, just as if it were a regular registration. There are two relevant code paths: Confirmation email is sent, and the unique link is clicked. User is sent to /confirm/:code and user.email.confirmByCode is executed, followed by user.email.confirmByUid The user email is confirmed without a code; only user.email.confirmByUid is executed (see below). If you want to create a user with a confirmed email, but don't want a welcome/confirmation email sent, you will need to manually set the email into the user, and run user.email.confirmByUid:const emailToSet = '[email protected]'; await user.setUserField(uid, 'email', emailToSet); await user.email.confirmByUid(uid); To my knowledge, there is a single case where a user may have their email set in the user hash, but not be confirmed: Users created before v1.18.0 will have an email set that may or may not be confirmed, as that was the behaviour prior to this change. I recommend you either remove the user's email, or confirm it. There are no ill effects to having a user account set up like this, although they may not show up in user searches if the query is an email address.

Hi,

i recently tried to launch, but I didnt manage to get my forum running on a server. I will get help for that soon. Until then i want to switch back from nginx proxy to localhost for some adjustments. I thought i just have to change the nodebb config file url back to localhost: ("http://localhost:4567/") but that doesnt seem to work. What am I doing wrong? my config file:

{
"url": "http://localhost:4567/",
"secret": "1130029f-733e-4dc3-a8a5-c3cf6b2b0d2c",
"database": "mongo",
"mongo": {
"host": "127.0.0.1",
"port": "27017",
"username": "nodebb",
"password": "nix",
"database": "nodebb",
"uri": ""
},
"port": "4567"
}

Hey, something looks different here... I can't quite place my finger on it 🤔

In this month's developer update, we'll keep it short and sweet. Three new updates, one major, and two minor.

v3 beta has arrived

Today we released beta versions of NodeBB (v3.0.0-beta.1) and the Harmony theme (v1.0.0-beta.1). This milestone is mostly symbolic, and signifies that we've reached a point where most or all of the pages in the theme have been re-designed, and are ready for more widespread testing.

While we don't consider v3.0.0 or the Harmony theme production-ready for anyone other than ourselves, we certainly wouldn't mind it if you tried using it. Since both Persona and Harmony are compatible on the v3.x beta, you can switch back and forth to try it out.

Let us know what you think, and let us know if you find any bugs. There will be bugs... the real question is how many 🙈

Updated drafts support

This month Baris worked on refactoring the drafts system to better handle the design needs of the Harmony theme. If a picture is worth 1000 words, how many is a gif worth?

drafts.gif

Instead of being limited to one draft per category/topic, you can nowcreate multiple drafts. Baris also fixed up some bugs related to drafts when editing posts.

Push Notifications via ntfy

We've been following along with the news about UnifiedPush and are excited to see where it will go. We've had trouble with various push notification implementations, and have experimented with a couple, with no reliable results:

The desktop notifications plugin often didn't work if the app was closed or inactive due to system battery constraints (so, basically all of the time) PushBullet monetized, and we decided to discontinue work on the plugin, as it was not a solution available to everyone. The firebase plugin worked quite well, although had zero support on Apple devices, which made it a no-go.

This is why I was very excited when I discovered ntfy.sh, a hosted pub-sub service that can act as a gateway for push notifications on browser and on mobile devices (iOS included)!

What sealed the deal for me was the fact that the author maintains an open-sourced server solution, so you are able to support your own server if you like, instead of using the ntfy.sh server. It'll allow our implementation to be used in the future, when ntfy.sh decides to monetize their service.

To that end, I've created nodebb-plugin-ntfy, bundled with v3.0.0-beta.1, which allows you to subscribe to push notifications on your phone/browser — give it a try!

You can access the push notification settings via your user settings menu:

4a7f8c63-be29-4d3c-b43d-0ca39782cc4a-image.png

Ive noticed that a few people here have custom badges such as "theme developer" / "plugin developer" - and I was wondering how to do some thing for my own forum?

I tried to do so for my own forum - but when we create a new group with this new badge - it does not show up beside the user..... at all.

We do have a the rewards plugin that assigns badges based on fulfilled conditions installed - which works for other badge titles that have conditions associated with them - but it does not work on a badge that has no condition associated with it.

Any help would be appreciated.

This is a bit of a silly one… but in advance of NodeBB v1.19.2, I wanted to take a minute and announce that we’ll be supporting animated GIFs in post uploads and user avatars! Technically, this is not anything new. NodeBB did support animated GIFs via the ImageMagick plugin, but that has always been an […]

Click here to see the full blog post

Id like to override a helper method in NodeBB/public/src/modules/helpers.common.js >> buildCategoryLabel

I want add my own custom class, so I can easily customize the topic badge. It seems like overkill to have to override 2 templates to achieve this. partials/topics_list.tpl topic.tpl

how would I go about this?

After filling out the Web Installer form and then running ./nodebb start on the command line. I get the errors listed below.
It seems like the Web Installer is still using the 4567 port the node server is trying to use.
I have tried killing all node processes before running ./nodebb start but the processes refuse to be killed and this has no effect.

Any suggestions?

./nodebb start errors Starting NodeBB "./nodebb stop" to stop the NodeBB server "./nodebb log" to view server output "./nodebb help" for more commands NodeBB v2.8.5 Copyright (C) 2013-2023 NodeBB Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For the full license, please visit: http://www.gnu.org/copyleft/gpl.html Clustering enabled: Spinning up 1 process(es). 2023-01-31T18:55:54.079Z [4567/192] - info: Initializing NodeBB v2.8.5 https://node.mydomain.com 2023-01-31T18:55:56.476Z [4567/192] - info: [socket.io] Restricting access to origin: https://node.mydomain.com:* (node:192) [LRU_CACHE_UNBOUNDED] UnboundedCacheWarning: TTL caching without ttlAutopurge, max, or maxSize can result in unbounded memory consumption. (Use `node --trace-warnings ...` to show where the warning was created) 2023-01-31T18:55:56.727Z [4567/192] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it. * nodebb-rewards-essentials 2023-01-31T18:55:56.837Z [4567/192] - info: [api] Adding 0 route(s) to `api/v3/plugins` 2023-01-31T18:55:56.853Z [4567/192] - info: [router] Routes added 2023-01-31T18:55:56.865Z [4567/192] - info: 🎉 NodeBB Ready 2023-01-31T18:55:56.867Z [4567/192] - info: 🤝 Enabling 'trust proxy' 2023-01-31T18:55:56.870Z [4567/192] - error: NodeBB address in use, exiting... Error: listen EADDRINUSE: address already in use 0.0.0.0:4567 at Server.setupListenHandle [as _listen2] (node:net:1733:16) at listenInCluster (node:net:1781:12) at doListen (node:net:1930:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2023-01-31T18:55:56.874Z [4567/192] - error: uncaughtException: listen EADDRINUSE: address already in use 0.0.0.0:4567 Error: listen EADDRINUSE: address already in use 0.0.0.0:4567 at Server.setupListenHandle [as _listen2] (node:net:1733:16) at listenInCluster (node:net:1781:12) at doListen (node:net:1930:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {"date":"Tue Jan 31 2023 18:55:56 GMT+0000 (Coordinated Universal Time)","error":{"address":"0.0.0.0","code":"EADDRINUSE","errno":-98,"port":4567,"syscall":"listen"},"exception":true,"os":{"loadavg":[0.81,0.68,0.78],"uptime":603592.54},"process":{"argv":["/usr/local/bin/node","/usr/src/app/app.js"],"cwd":"/usr/src/app","execPath":"/usr/local/bin/node","gid":1000,"memoryUsage":{"arrayBuffers":869872,"external":2935100,"heapTotal":110329856,"heapUsed":78592824,"rss":174796800},"pid":192,"uid":1000,"version":"v18.13.0"},"stack":"Error: listen EADDRINUSE: address already in use 0.0.0.0:4567\n at Server.setupListenHandle [as _listen2] (node:net:1733:16)\n at listenInCluster (node:net:1781:12)\n at doListen (node:net:1930:7)\n at process.processTicksAndRejections (node:internal/process/task_queues:83:21)","trace":[{"column":16,"file":"node:net","function":"Server.setupListenHandle [as _listen2]","line":1733,"method":"setupListenHandle [as _listen2]","native":false},{"column":12,"file":"node:net","function":"listenInCluster","line":1781,"method":null,"native":false},{"column":7,"file":"node:net","function":"doListen","line":1930,"method":null,"native":false},{"column":21,"file":"node:internal/process/task_queues","function":"process.processTicksAndRejections","line":83,"method":"processTicksAndRejections","native":false}]} 2023-01-31T18:55:56.875Z [4567/192] - error: Error: listen EADDRINUSE: address already in use 0.0.0.0:4567 at Server.setupListenHandle [as _listen2] (node:net:1733:16) at listenInCluster (node:net:1781:12) at doListen (node:net:1930:7) at process.processTicksAndRejections (node:internal/process/task_queues:83:21) 2023-01-31T18:55:56.875Z [4567/192] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. 2023-01-31T18:55:56.878Z [4567/192] - error: Error [ERR_SERVER_NOT_RUNNING]: Server is not running. at new NodeError (node:internal/errors:400:5) at Server.close (node:net:2075:12) at Object.onceWrapper (node:events:627:28) at Server.emit (node:events:525:35) at emitCloseNT (node:net:2128:8) at process.processTicksAndRejections (node:internal/process/task_queues:81:21) [cluster] Child Process (192) has exited (code: 1, signal: null) [cluster] Spinning up another process... ----- snip ----- # Repeats the above 2 more times 3 restarts in 10 seconds, most likely an error on startup. Halting.

Hi, I have created a custom private plugin for nodebb platform for a client. It is like the session-sharing plugin, handling sso with jwt but with a custom implementation. I need to create a setting page inside ACP for my plugin as session-sharing has. so I can put some dynamic values for cookies i.e; domains, token names, etc.

Is there any doc for creating a setting page or something similar? I cannot find anything useful in nodebb docs relevant to it.

thanks

The Quickstart plugin has everything you need to get started, including an example of how to create a settings page for the plugin.

However, it is not readily apparent what parts of the code pertain to that ask, so this topic tries to disambiguate.

To create a settings page in the ACP, you'll want to do five things.

Create a template so you can add your form fields, etc. Mount a route that loads that template Have a link to that template show up in the ACP navigation Allow settings to be saved Access those settings from within your library.js Create a template so you can add your form fields, etc.

In plugin-quickstart, you can see where templates are defined by checking plugin.json:

"templates": "static/templates"

Any templates you add to this directory will be merged with NodeBB's core template files, and bundled together during ./nodebb build. Any templates you define that conflict with core templates override the core template.

You'll notice a template file: static/templates/admin/plugins/quickstart.tpl

Since this is your own plugin, you'll want to rename this file to something more relevant, e.g. foobar.tpl.

Update the template as necessary to include any settings you'd like to define. Later on, we'll be using the NodeBB-provided settings module to persist settings to the database, so the only considerations for the template are:

That a <form> element exists with a corresponding className, e.g. <form role="form" class="foobar-settings"> That form fields have a name attribute (these names are the property names saved into the database) That a save button exists. You can probably use this partial: <!-- IMPORT admin/partials/save_button.tpl -->. add it to the bottom of the template if it's not there already. Mount a route that loads that template

To do this, you'll need to listen to the static:app.load hook (see how it is registered in plugin-quickstart, here).

We call the helper function .setupAdminPageRoute in order to mount the route:

routeHelpers.setupAdminPageRoute(router, '/admin/plugins/quickstart', [], controllers.renderAdminPage); Have a link to that template show up in the ACP navigation

To do this, you'll need to listen to the filter:admin.header.build hook (see how it is registered in plugin-quickstart, here).

Relevant code:

plugin.addAdminNavigation = (header) => { header.plugins.push({ route: '/plugins/quickstart', icon: 'fa-tint', name: 'Quickstart', }); return header; }; Allow settings to be saved

The modules property allows you to define require.js or CommonJS modules that can be automatically run by NodeBB (or imported/required via other files).

You can add one for ../admin/plugins/foobar.js.

Note: ../admin and ../client are magic keywords that allow NodeBB to determine whether a module is loaded for the ACP or for a client-side page. NodeBB will load the corresponding file based on template name, and if a method called init() exists, will execute it.

If you look inside static/lib/admin.js, you'll see the code that wires up the form and hooks into the Settings module in NodeBB.

You probably also want to change the module name too:

define('admin/plugins/foobar', [... Access those settings from within your library.js

Lastly, now that the mount is routed and settings can be saved, you can retrieve them from within your library.js by directly invoking the meta module:

const { mySetting } = await meta.settings.get('foobar');

Hello, is there any way I can disable file logging? I only need the console output logging. I can see this code for web install logging:

winston.configure({ level: 'verbose', format: winston.format.combine.apply(null, formats), transports: [ new winston.transports.Console({ handleExceptions: true, }), new winston.transports.File({ filename: 'logs/webinstall.log', handleExceptions: true, }), ], });

But not for global logging system. Thanks in advance.

I have lost access to my forum.

Sequence of steps:

Installing a new instance on the server. Server behind Cloudflare. Initially, I did not receive a local certificate, everything worked behind a Cloudflare certificate. Transferring the database from a local instance (worked on Mac OS) to the server. Successful login, further setting in the admin panel. The forum has been switched to maintenance mode. After some time, I notice that I can't log in to another browser. I am getting an invalid username or password error. I can still work in the admin panel. After some time, I am thrown out of the admin panel. And now I'm logged in to the forum (I see all topics, although the forum is in maintenance mode), but to enter the admin panel, a login / password page opens, which the system does not accept.

I've tried almost everything. I set up a local certificate and tried to access the forum directly bypassing Cloudflare. I have enabled developer mode (no cache) and full SSL/TLS on Cloudflare. The problem is obviously not this.

Next, I reset the cookie domain: db.objects.update({_key: "config"}, {$set: {cookieDomain: ""}});
Also no effect. I do not understand what the problem is. I have already read all the threads on this forum regarding authentication failures and have probably tried all the recipes.

Forum: https://kimry.net

NodeBB v2.8.5
Node.js v18.13.0.
MongoDB 6.0.4
Ubuntu 22.04.1

Nginx config:

server { listen 80; server_name kimry.net; return 301 https://$server_name$request_uri; } server { listen 443 ssl http2; server_name kimry.net; ssl_certificate /etc/nginx/ssl/kimry.net/cert.pem; ssl_certificate_key /etc/nginx/ssl/kimry.net/key.pem; ssl_dhparam /etc/nginx/ssl/kimry.net/dhparams.pem; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:4567; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } }

config.json

{ "url": "https://kimry.net", "secret": "----", "database": "mongo", "mongo": { "host": "127.0.0.1", "port": "27017", "username": "nodebb", "password": ----- "database": "nodebb", "uri": "" } }