[nodebb-plugin-reactions] Reactions plugin for NodeBB

prodigal_halogen

Hello, I am trying to install this plugin with no success. I am running a Cloudron instance of node BB, and I can access the terminal (which, if I'm not mistaken, takes me to the docker container in which the node BB instance is installed/running.

My understanding is that the node BB community version of this plugin is no longer maintained actively and should not be expected to work.

However, it seems that there is a new, more maintained version. Here's what I tried:

user@site:/app/code# npm i @nodebb/nodebb-plugin-reactions      
npm WARN reify Removing non-directory /app/code/node_modules
npm ERR! code EROFS
npm ERR! syscall unlink
npm ERR! path /app/code/node_modules
npm ERR! errno -30
npm ERR! rofs EROFS: read-only file system, unlink '/app/code/node_modules'
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

I also tried npm i @nodebb/[email protected], which gave the same output.

Any help installing this would be greatly appreciated.

NodeBB 2.3.1

julian

@prodigal_halogen Might be you need to reach out to the Cloudron team to ask what is happening.

It looks like it's trying to remove the node_modules/ folder, which is probably not what you want

dave1904

I would like to implement notifications for this plugin. I have seen that @eshohet did a WIP implementation here: https://community.nodebb.org/topic/12332/new-features-for-nodebb-plugin-reactions. As that topic is nearly 5 years old and code has changed, did someone implement notifications for this plugin and using it today?

julian

I believe @pichalite is not active with NodeBB community anymore, but it is possible we will reintroduce another reactions plugin as it seems to be fairly popular

dave1904

@julian

Yes in our forum it is used quite often and it would be a helpful feature if a user gets feedback in form of a notification when another user has reacted to a post. I will stay tuned for a possible new plugin.

phenomlab

Anyone else noticed significant lag (and I'm talking 2 seconds for each click) as soon as you add a reaction to a post? Reloading the browser fixes the issue, but not great at all from the user experience.

Seems that my socket.io load has increased dramatically with this plugin, along with significant increase in CPU cycles. Based on this, I'm removing it, but leaving a note here to hopefully fix that as it's a useful plugin.

dave1904

@phenomlab

I don't have this issue (v1.0.2 and nodeBB v2.8.5).

phenomlab

@dave1904 interesting. I was able to reproduce this issue across 4 browsers and also on my virtual machine as well as my production server.

dave1904

@phenomlab Maybe interfering with another plugin? Did you update anything before the issue appeared? Or did you just install it?

phenomlab

@dave1904 just installed it. The other environment was a vanilla install with only the base plugins

julian

@phenomlab are you running reactions on a v3.x instance?

phenomlab

@julian no. V2

josef

I fixed and improved all kinds of things in this plugin, and it is now fully compatible with nodebb v3!
https://github.com/NodeBB-Community/nodebb-plugin-reactions

crazycells

@josef thanks

DownPW

hello @josef @baris

I have upgraded nodebb 3.0.1 to 3.1.1 and @nodebb/nodebb-plugin-reactions to 2.0.0 and now I have this error on start log with this plugin :

And this when I want to add reaction on posts :

Console browser log :

DownPW

@baris

Uninstall and reinstall plugin and it's OK now
Seems broken upgrade package

josef

@DownPW
By the way, I added an option to limit reactions per post per user, ~~it's in PR, if you want you can install from there~~ published in 2.0.1 version

DownPW

Very good option and very good plugin
Thanks

DownPW

@josef

I have test on second instance and same problem the upgrade is broken when I upgrade nodeBB

I have uninstall and reinstall the plugin (2.0.1) but this time, I have not the icon for add reaction on topic.
No error on build

josef

@DownPW
I don't know what can be done...
Try to rebuild