It is stored in the config
object.
> db.objects.findOne({_key: "config"}).customCSS
.best {
background-color: #ff0000;
}
It is stored in the config
object.
> db.objects.findOne({_key: "config"}).customCSS
.best {
background-color: #ff0000;
}
nodebb-plugin-tenor-gif
nodebb-plugin-recent-cards
nodebb-theme-persona
nodebb-plugin-soundpack-default
nodebb-plugin-spam-be-gone
nodebb-plugin-blog-comments
nodebb-widget-essentials
nodebb-rewards-essentials
nodebb-plugin-mentions
nodebb-plugin-markdown
nodebb-plugin-canned-responses
nodebb-plugin-imagemagick
nodebb-plugin-question-and-answer
nodebb-plugin-composer-default
nodebb-plugin-2factor
nodebb-plugin-sso-facebook
nodebb-plugin-google-analytics
nodebb-plugin-sso-google
nodebb-plugin-emoji
nodebb-plugin-firebase
nodebb-plugin-emailer-sendgrid
nodebb-plugin-sso-github
nodebb-plugin-sso-twitter
nodebb-plugin-browsing-users
nodebb-plugin-openapi-spec
nodebb-plugin-iframely
nodebb-plugin-dbsearch
nodebb-plugin-imgur
nodebb-plugin-registration-question
nodebb-plugin-github-embed
nodebb-plugin-emoji-android
Related issue https://github.com/NodeBB/NodeBB/issues/4587
As discussed in the issue, we had a bunch of hooks to modify a page on some routes like filter:recent.build
. These were added as required but most pages didn't have a hook so if you needed one you would have to ask us to add it and wait for the next release. With the above change every route has a hook. The hook name is derived from the template name passed to the res.render(template, data);
method. For example if your template is named myAwesomePage
, you render it with res.render('myAwesomePage', data);
and the hook that will be fired is filter:myAwesomePage.build
Every hook gets 3 parameters {req: req, res: res, templateData: data}
, data is the parameter you pass into the res.render
method.
We had a few inconsistencies in the parameters passed to the hook and the hook name below are the changes that needs to be fixed if you have a plugin that is listening to these hooks.
filter:groups.build
is now called filter:group/details.build
as that is the correct name for that template.filter:popular.build
used to pass in a extra term
parameter, this moved into the templateData parameter.filter:header.build
this is removed it was deprecated a while ago. Use filter:navigation.available
instead.filter:search.build
parameters changed, data is no longer passed in use req.query and req.params instead. results is now the templateData parameter.Feel free to ask any questions if anything isn't clear.
Enable post queue if you are getting spam. It puts the posts of new users in a queue for approval before they become visible.
The latest version of this plugin(1.0.1) is compatible with NodeBB 1.18.3.
This is a new feature that is coming in 1.6.1, previously html widgets were just static. Now you can use them like any template. For example here is a sample html widget placed on category.tpl sidebar.
Now when you visit the General Discussion
category it looks like this:
If you visit Announcements Category
it looks like this:
You can use any benchpressjs(templates.js) syntax, and any data that is avaiable in ajaxify.data
. You can see the variables available by opening up your browser console and typing ajaxify.data
.
Another cool feature this allows is letting plugins add custom data into pages and then utilizing that in widgets. By using the hooks filter:<template_name>.build
and/or filter:middleware.render
you can add data into the page and the widget will have access to the same data.
Hope this helps customise your NodeBB even further!
The lights are done with
body {
background-image: url('https://community.nodebb.org/assets/uploads/files/xmas-lights.png');
background-repeat: repeat-x;
background-position: top -20px left;
}
The snowman is some custom JS.
$(window).on('action:ajaxify.end', function(ev, data) {
if (!$('#snow-man').length) {
$(`<img
src="https://www.freeiconspng.com/thumbs/snowman-png/snowman-png-29.png"
id="snow-man"
class="d-none d-lg-block position-fixed pe-none" style="z-index: 1054; bottom: -50px; right: -100px;"/>
`).appendTo('body');
}
});
We will release 2.0 I am going to keep a list of plugins here that are compatible already. If you have any plugins that are not in this list let us know and we will try to get them updated before release.
The migration guide is here.
Hi Everyone,
We are going to be introducing a plugin usage metrics system in 1.13.0. Up until now, the plugins page at admin/extend/plugins#download showed all plugins published to npm with no way to see if the plugin was compatible with your version of NodeBB. This lead to the installation of plugins that might potentially crash your nodebb on startup.
To change this, we are adding a new opt-in system that submits the plugins that are active on your forum to nbbpm.
Here are some details about this system:
"private": true
in their plugin.json./nodebb setup
You can see the exact data that is submitted here.
You can opt-in or out anytime from /admin/extend/plugins. If a plugin has no compatibility data available it will show a warning like this
If the plugin has compatibility data it will show a notice like this
Yeah I think having a folder under public/uploads/profile for each user would make deleting easier. We can get rid of the glob and delete that folder on user deletion. But we would have to write an upgrade script to move all files and update the path in the user object since they are stored as "/assets/uploads/profile/1-profileavatar-1709738685611.jpeg"
Hi everyone!
We just released version 1.5.1, for a list of all issues closed in this release please take a look at the 1.5.1 Milestone.
Please report any issues on our tracker at github. If you have any questions about installation or troubleshooting please post them on our Technical Support category.
We recently received some inquiries about how long we will support 1.x and 2.x with security fixes.
We also released https://github.com/NodeBB/NodeBB/releases/tag/v2.8.16 and https://github.com/NodeBB/NodeBB/releases/tag/v1.19.12 containing some of the fixes from the 3.x line. If you are not able to upgrade to 3.x we encourage you to upgrade to these releases.
Added a new option to change the notification setting for chat rooms.
Administrators can change the room default from the manage room modal.
I rewrote the plugin and published as @nodebb/[email protected]
.
Or lighter so it has some contrast to the content area
@phenomlab I am offended
@sweetp Yeah forgot to mention that, 3.4.0 has the updated dark sidebar as well
Updated the list, it might be better to use a public wiki so people can add remove this info.