Hi nodebb-Community,

I'm using a customized shell script to manage 3 nodebb environments (local/staging/production). This is helping to integrate and customize private modules on the server, etc. - and activates/resets default modules for our setup.

Now I wonder how to go about "default settings" - e. g. I want to get sure the site-name is consistent everywhere - or vice versa, set it dynamically depending on the environment.

Does nodebb has an API for setting settings through shell?
Or would I need to go through the mongo shell?

Hi @davidr I'm just about to do the same thing.

I'm using a custom theme, so I will be adding it there, can tell you more, when I'll start this.
Do you use a custom theme?

@pitaj Thanks for your answer! The npm@5-symlink-deletion was my main problem, so my command is working again. I would love to see it in the Documentations for future look-ups.

I've anyhow tried using your suggested command with my params ./nodebb setup --params, but it's not working:

• error: unknown option '--setup' - on the first try, then I deleted the setup param
• error: unknown option '--defaultPlugins' - also unknown

I'm on the v1.7.5 branch.

Hi Community,
this piece of code used to work in a custom setup-script:

    node app.js \
        --setup "{\"admin:username\":\"${ADMIN_USERNAME}\",\"admin:password\":\"${ADMIN_PASSWORD}\",\"admin:password:confirm\":\"${ADMIN_PASSWORD}\",\"admin:email\":\"${ADMIN_EMAIL}\"}" \
        --defaultPlugins "[\"nodebb-plugin-custom-homepage\", \"nodebb-plugin-custom-pages\", \"nodebb-plugin-dbsearch\", \"nodebb-plugin-emoji\", \"nodebb-plugin-emoji-android\", \"nodebb-plugin-emoji-extended\", \"nodebb-plugin-emoji-one\", \"nodebb-plugin-markdown\", \"nodebb-plugin-mentions\", \"nodebb-plugin-ns-embed\", \"nodebb-plugin-soundpack-default\", \"nodebb-plugin-spam-be-gone\", \"nodebb-rewards-essentials\", \"nodebb-theme-vanilla\", \"nodebb-widget-essentials\"${modulesToActivate}]" \
         || (echo "Unable to install nodebb" && exit 1)

modulesToActivate has a string continuing the array of plugins.

This seems so have changed. It also seem to delete symlinks created in the node_modules folder.

Did anything change?
Or what is the currently recommended way to install from CLI?

@baris Thank you very much for the example. I use a custom theme and this works perfectly as expected in some parts of the template. I changed it in the following files:

modules/nodebb-theme-name/templates/partials/menu.tpl
modules/nodebb-theme-name/templates/partials/account/header.tpl
modules/nodebb-theme-name/templates/account/edit.tpl

And it's working. A new uploaded profile-picture is immediately shown after upload, also without deleting the browser-cache.

Now in the upload-modal:
modules/nodebb-theme-name/templates/partials/modals/change_picture_modal.tpl
the old picture is still shown. Adding the cacheBuster-query-string there doesn't work, the timestamp is not appended. Is there a hook also for this case?

Also is there a list of all possible hooks/events that are happening in the system?

Another thing I noticed is, that after uploading a new profile-picture, the success-callback changes the picture in the header-menu and in the edit-page immediately, but not in the profile-header part (after refreshing, with the new cacheBuster, it is changed).
I've traced it to this file: app/public/src/client/account/edit.js.
How can I now react on the image-change in my custom theme?

Hi nodeBB-Community,
we are using nodebb 1.4.6 and I'd like to cache-bust the profile-avatars, so changes are immediately seen by every user.

How can I use Date.now() inside a template?

@julian I've just stumbled upon the same issue.

I wanna get around it, what possibilities do I have, as our upcoming user-base will not be technically advanced and they'll blame the system.

Is there anywhere a timestamp of the last changed avatar? Or how can I use a Date.now() cache-buster inside the template?

@chaosyamyt it seems this is the repo for that:
https://github.com/esiao/nodebb-plugin-custom-header

You could try to check it out into the "node_modules" directory and then activate it in the admin-interface.

Hi @Ottman001,

either you are not using SMTP, then your NodeBB uses the server's sendmail() function, and you'll have to check your configuration on the server
(for example like explained here).

Or you use SMTP, then you could try to login to your admin and go to this URL: http://yourdomain.com/admin/emailers/local

If you do use SMTP, then it's odd that you don't have installed any plugin nor that there is any menu-entry for the SMTP-configuration

Best regards,
Sebastian

@Shard Looks interesting! Thanks for sharing

@PitaJ thanks for that info. I'm on v1.x.x, and probably will stay there for the next time, but now I have a reason to think about upgrading

@baris thanks, that is exactly what I looked for:

        var userProvidedCatIds = widget.data.catIds;

        if (!userProvidedCatIds || userProvidedCatIds === '0') {
            categories.getCategoriesByPrivilege('cid:0:children', widget.uid, 'find', render);
        } else {
            categories.getCategories(userProvidedCatIds.split(',').map(Number), widget.uid, render);
        }

        function render(err, data) {
            app.render('categories.tpl', {
                categories: data,
                relative_path: nconf.get('relative_path')
            }, function (err, html) {
                widget.html = html;
                callback(err, html);
            });
        }

Is there any doc-site / rtfm for the JS-API or do we have to look at the source to find appropriate methods and their parameters?

Just googled for this. Yeah, it would be nice to suppress these
Anyone any idea where they come from?

Edit:

Found the answer: https://github.com/NodeBB/NodeBB/issues/5695

@PitaJ thanks for the info

@PitaJ Thanks for that information and the fix!

Could this also be merged as patch into the v1.x.x-branch?

Hi nodebb-community,

I'm developing a widget that shows categories in material-cards-style on the homepage.

At the start there were only 4 root-categories, so it looked good. Now there will be 5 root-categories and that won't look good anymore. In library.js my render-function looks like this:

    Widget.renderMaterialCategoriesWidget = function(widget, callback) {
        categories.getCategoriesByPrivilege('cid:0:children', widget.uid, 'find', function(err, data) {
            app.render('categories.tpl', {
                categories: data,
                relative_path: nconf.get('relative_path')
            }, function (err, html) {
                widget.html = html;
                callback(err, html);
            });
        });
    };

I'm interested in this part: categories.getCategoriesByPrivilege('cid:0:children', ..., ...)
Can I provide an array of category-ids? Or is there any other way/function I can use to specify the categories I want to render?

@baris Thanks for the info.

So the fact that I'm not seeing it has, as I just researched, to do with the used theme
Will update from the default-theme.

Hi nodebb-community,

I forked nodebb-plugin-featured-topics-extended and tried adding a German translation file:

The file has German text-translations in it. If I now go into app/build/public/language/de, the fte.json is the English version.

The plugin.json has still the "languages": "public/language" entry.
This forked version of the plugin is inside a symlinked directory, but that shouldn't bother.

My changes can be seen at my Github-commit.

What am I doing wrong or what could be going wrong?

Hi @psychobunny did you finish it?

If not, do you know what this forum uses for the "n Reply"-functionality on the bottom of a post?

So after researching a little more I found my answer inside the plugin.json of the quickstart-plugin.

"staticDirs": {
	"images": "./images" 
},

Adding a staticDirs key inside the plugin.json like that adds the static dirs inside /assets/plugins/your-plugin-name/.