NodeBB Awards

Plugin for adding Award System on your board: it could be medals, or it could be very special ranks, etc. It's a good instrument to engage users on your board, and It's another instrument for gamification of your board.

I hope this plugin will be helpful for you

Install

npm install nodebb-plugin-ns-awards

Links

• Plugin
• Issues
• Changelog

Features Overview, pre-release

All components will be improved overtime. It's just very first steps If you have ideas, don't hesitate to share them.

Create Awards

Overview them in ACP

Give Medals!

Overview all awards at yourboard.com/awards

Extend user's profiles

NodeBB: Twitch Monitor

Monitors specific channels in real time and adds them to the widget view.

Install

npm install nodebb-plugin-ns-twitch-monitor

or via plugin manager

Links

• Plugin
• Issues
• Details

Video Preview

NodeBB: Twitch Monitor Prevew, ver. 1.0.0

Widget Look

NodeBB Likes

Tradional Like system, like on various social networks. This plugin uses NodeBB Vote System, but as you can see only up-votes
Same as default chevrons, plugin uses sockets to update in real-time.

Links

• Plugin
• Issues
• Theme configuration

How does it look like?

It's a small widget (Bootstrap, extra small button).

It's a split button:

• left part is toggle button, to like/unlike
• right part is count button, to show likers

Provides full set of instruments to create custom fields in user's profiles: admin control panel (manage available fields), user account (edit and view fields);

• Plugin
• Issues
• Changelog
• Feature requests: this thread is ok

Install

npm install nodebb-plugin-ns-custom-fields

ACP

Preview of Admin Control Panel for Custom Fields Plugin, ver. 1.0

Theme Status

Currently zero themes support this plugin. With template engine of NodeBB, some changes should be made manually to the theme, if you want to see custom fields in the user's profile.

It will look like:

NodeBB Points

Additional metrics for User Profiles. It's like experience in video games. Plugin is good for gamification of your board. It's another plugin without which I can't migrate to NodeBB I have found such approach interesting over years. Basically Points is more precise instrument to measure user activity. Also this plugin teaches users to be good to each other.

Treat points as experience, at current state (v1.0.0), plugin takes into account: posts, topics and reputation (only good one, up-voting )

Install

Developed with NodeBB 0.7.0

npm install nodebb-plugin-ns-points

Useful links:

• Plugin
• Issues
• Changelog

Overview Page

You can reach it via yourforum.com/points url. Seems, in 0.7.0 you should add link yourself Overview page uses default function for rank calculation. Number on avatar is Level, like in RP Games

Themes

Here is very basic example, how you can display raw points to visitors:

NodeBB Utils

Set of utility functions to help you support your forum. Do you need to purge chats? Do you need to delete obsolete data? This plugin will help you.

Small story: I had to purge chats (I did a mistake in import script), and decided to share such type of work as a plugin. I could just purge chats via mongo client, but I have gone in plugin direction, It took me 100 times more time to finish with purging task

Compatible with 0.8.2 and primary dabase - MongoDB. Install plugin via Plugins section in ACP.

Useful links:

• Plugin
• Issues

Overview

NodeBB: Spoiler

Spoiler. Ability to control visibility of the content in posts. Works better with Markdown syntax. Integrates with default composer, so you will have additional button on toolbar.

Compatibility Note: should work with 0.8 and 0.9. Tested on 0.8.

Useful links:

• Plugin
• How to use

Preview:

NodeBB: Spoiler Prevew, ver. 1.0.0

Awards ver. 4

A new version has been released. It's a major release. It took a while to make all changes.

Changelog:

• Add an edit mode for multiple awards
• Add support for plugin driven image upload
• Add rewards section to ACP
• Add protection for an image upload service
• Add activity limit setting
• Add configuration for notification text
• Add reward multiplier for overview page
• Add external Plugin API
• Add tooltips to a topic view
• Add support for SVG
• Change UX for the creation of awards
• Change UX for Overview section
• Change award URL to use an absolute path
• Change award upload
• Change NodeBB compatibility to v1.5.x and higher
• Change notifications
• Change max rewards per post setting
• Change max rewards per account setting
• Change overview page styles to use Flexbox
• Update plugin dependencies
• Update ACP dependencies
• Remove extended profile template

It also provides a new UX, and it should be easier to style for your own needs.

Widget: Birthdays

Widget to show all today's birthdays. Works well with Sidebars in your theme. Customization is available through CSS. More details could be found in the widget's repository. Install it via widget manager.

If you don't want to show user's age, you can disable it in widget's settings.

Links

• Issues
• Changelog

Look

Version 2.1.0

New version is available. Summary: Manage section.

• Update user delete hook to static:user.delete
• Fix #6 issue with limit when user is deleted
• Improve Autocomplete component: clear search result
• Introduce Manage section: ability to reward multiple users; manage user's awards;
• Updated libraries for ACP

Preview

NodeBB: Awards Preview, Manage, ver. 2.1.0

Thank you everybody for helping me with forum troubleshooting. The problem has been found. It's memory limit. After a few years of use, 512MB RAM + 256MB swap is not enough anymore (I have some suspicions that swap does not kick in, but it's a topic for a different story).

If somebody searches, and no changes plugins, core, or hardware, and you do not have plugins that depend on external services - check if it's a memory issue.

@baris yep. Sounds are not the problem, the result is the same with the disabled sound step.

Interesting if memory is an issue now. Yes, it's a 512MB server, for some reason, it's a limit now after 5 years?..
When I look at htop, it peaks at max memory when forum startups, but it was not an issue before.

I can try to ask the provider to give more memory to check the hypothesis and let you know if it helped.

I have switched your proposed extra flow with console logs to parallel, and receive these results:

1
2.sounds
5/3 04:54 [31928] - error: [sounds] Could not initialise sounds: EEXIST: file already exists, symlink '/web/overseers/node/forum/public/uploads/sounds/.gitignore' -> '/web/overseers/node/forum/public/sounds/.gitignore'
2.blaclist
2.b.minifycss
2.b.minify
5/3 04:54 [31928] - info: NodeBB Ready
5/3 04:54 [31928] - info: Enabling 'trust proxy'
2.compile
5/3 04:54 [31928] - info: NodeBB is now listening on: 0.0.0.0:8081

A bit weird results. You have switched to waterfall, now it goes to the next step, but chokes there.

1
2
2.compile
2.b.minify
2.b.minifyjs
5/3 04:41 [31364] - info: NodeBB Ready
5/3 04:41 [31364] - info: Enabling 'trust proxy'
2.b.minifycss
5/3 04:41 [31364] - info: NodeBB is now listening on: 0.0.0.0:8081
2.sounds
2.blaclist
3

Reverted back to parallel:

1
2

@baris It did not print 3

I feel we are very close. @baris Thank you for looking into this!

It chokes here - https://github.com/NodeBB/NodeBB/blob/v1.0.2/src/webserver.js#L92-L101

I do not see console.log in the next waterfall step after template compilation.

@baris plugins command output:

$ ./nodebb plugins
5/3 04:06 [30726] - info: [database] Checking database indices.
5/3 04:06 [30726] - info: Active plugins:
	 - nodebb-theme-overseers
	 - nodebb-widget-essentials
	 - nodebb-plugin-soundpack-default
	 - nodebb-plugin-mentions
	 - nodebb-plugin-markdown
	 - nodebb-plugin-emoji-apple
	 - nodebb-plugin-emoji-extended
	 - nodebb-plugin-composer-default
	 - nodebb-plugin-ns-api
	 - nodebb-plugin-ns-likes
	 - nodebb-plugin-ns-login
	 - nodebb-plugin-ns-points
	 - nodebb-plugin-ns-slugify
	 - nodebb-plugin-write-api
	 - nodebb-plugin-ns-embed
	 - nodebb-plugin-dbsearch
	 - nodebb-plugin-ns-custom-fields
	 - nodebb-plugin-ns-awards
	 - nodebb-widget-ns-birthdays
	 - nodebb-widget-ns-stats
	 - nodebb-plugin-emailer-mailgun
	 - nodebb-plugin-google-analytics

Interesting, any of these plugins interact with external services maybe? That is why it's stopped working. If no changes to local plugins like my ("NS") or others, it should still work without any issues.

As for console.log, it's triggered for ./nodebb dev, but it is not triggered for ./nodebb start

@baris Git Status

$ git status
On branch v1.x.x
Your branch is up-to-date with 'origin/v1.x.x'.
nothing to commit, working directory clean

@PitaJ Git DIff is package.json only. Likely because I have plugins.

@psychobunny @baris what am I risking by running forum as NODE_ENV=development ./nodebb start?

So I'm debugging Express, in production, Route registration does not happen. For example, in debug mode I see logs like:

  express:router:route get /user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route new /api/user/:userslug/edit/password +0ms
  express:router:layer new /api/user/:userslug/edit/password +0ms
  express:router:route get /api/user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/edit/password +0ms
  express:router:layer new / +0ms
  express:router:route new /user/:userslug/settings +0ms
  express:router:layer new /user/:userslug/settings +0ms
  express:router:route get /user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/settings +1ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route new /api/user/:userslug/settings +0ms
  express:router:layer new /api/user/:userslug/settings +0ms
  express:router:route get /api/user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route get /api/user/:userslug/settings +0ms
  express:router:layer new / +0ms
  express:router:route new /user/:userslug/session/:uuid +0ms
  express:router:layer new /user/:userslug/session/:uuid +0ms
  express:router:route delete /user/:userslug/session/:uuid +0ms

But in production mode I can see only initial Express operations:

express:application set "x-powered-by" to true +0ms
  express:application set "etag" to 'weak' +1ms
  express:application set "etag fn" to [Function: wetag] +1ms
  express:application set "env" to 'development' +0ms
  express:application set "query parser" to 'extended' +0ms
  express:application set "query parser fn" to [Function: parseExtendedQueryString] +0ms
  express:application set "subdomain offset" to 2 +0ms
  express:application set "trust proxy" to false +0ms
  express:application set "trust proxy fn" to [Function: trustNone] +1ms
  express:application booting in development mode +0ms
  express:application set "view" to [Function: View] +0ms
  express:application set "views" to '/web/overseers/node/forum/views' +0ms
  express:application set "jsonp callback name" to 'callback' +0ms
  express:application set "view engine" to 'tpl' +85ms
  express:application set "views" to '/web/overseers/node/forum/public/templates' +1ms
  express:application set "json spaces" to 0 +0ms
  express:router use / query +0ms
  express:router:layer new / +1ms
  express:router use / expressInit +0ms
  express:router:layer new / +0ms
  express:router use / <anonymous> +0ms
  express:router:layer new / +0ms
  express:application set "view cache" to true +1ms
  express:router use / compression +0ms
  express:router:layer new / +0ms
  express:router use  favicon +0ms
  express:router:layer new  +0ms
  express:router use /apple-touch-icon <anonymous> +0ms
  express:router:layer new /apple-touch-icon +0ms
  express:router use / urlencodedParser +26ms
  express:router:layer new / +1ms
  express:router use / jsonParser +0ms
  express:router:layer new / +0ms
  express:router use / cookieParser +0ms
  express:router:layer new / +0ms
  express:router use / <anonymous> +1ms
  express:router:layer new / +0ms
  express:router use / session +0ms
  express:router:layer new / +0ms
  express:router use / <anonymous> +0ms
  express:router:layer new / +0ms
  express:router use / <anonymous> +1ms
  express:router:layer new / +0ms
  express:router use / initialize +0ms
  express:router:layer new / +0ms
  express:router use / authenticate +0ms
  express:router:layer new / +0ms
  express:router use / <anonymous> +0ms
  express:router:layer new / +0ms
  express:router use / <anonymous> +1ms
  express:router:layer new / +0ms
  express:application set "cache" to true +1ms
  express:application set "minification" to true +0ms

That is why even the basic root route does not work since none of them are registered. Any hints where to look next?