great @Ben-Lubar ! Thanks

The cron tab is for what exactly ?

Thank you again, now it seems to work well!

Can you review the code and maybe test the module?
I would like to be sure that I have not forgot something.

https://github.com/LM1LC3N7/nodebb-plugin-private-forum

@PitaJ said in Private forum plugin:

What you want is to add a new middleware that applies to all routes except those related to login and register.

Yes, you are totally right.

Do you have in mind a plugin that add a middleware in static:app.load handler?
It will be faster to clone and edit it

I will take a look at the documentation.

@pitaj Yes, this is why I don't understand. And I only stop the nodebb container, not the db container.

Hello all

I am creating my own docker container, and I have an issue with plugin being reactivating after a docker re-creation.

At container start (nodebb code & dependencies are already installed) :

1. nodebb setup
2. nodebb reset -p nodebb-plugin-composer-default
3. nodebb build
4. nodebb start

After each startup, the default composer is enabled again. Do you know why?

@baris My god, it's not good to work with bash and javascript at the same time (thank you btw)

My "old" code is still working well without depreciation warning, thanks for your answers

@baris infact I have installed the old version and I update the installed module directly (in node_modules folder).

I rebuild and restart nodebb, but the plugin version is still the old one.

Does my plugin file code looks ok to you?

@baris After a rebuild, reset module and activate again, still nothing.
I have manually changed the package.json version number but the old version still appears. An idea why? My updates are maybe never used?

Hello @baris and @magnusvhendin

I would like to update my module nodebb-plugin-private-forum that should do exactly what you are trying to archive.
But it seems it is not working well with v1.16.2 and I need some help on the Hook declaration.

I understand that I need to use response:router.page, but how exactly?
Is this ok for you?

plugin.json

{
  "id": "nodebb-plugin-private-forum",
  "url": "https://github.com/LM1LC3N7/nodebb-plugin-private-forum",
  "library": "./library.js",
  "hooks": [{
    "hook": "response:router.page", "method": "init"
  }]
}

library.json

'use strict';

const plugin = {};
var winston = module.parent.require('winston');
const helpers = require.main.require('./src/controllers/helpers');

plugin.init = async (data) => {

        const allowedPages = /\/(assets\/|login|register|reset|plugins\/).*|.*(.css|.js)$/;

        winston.verbose("[plugin-nodebb-private-forum] Checking URL ("+ req.url +"), redirection.");

        # Allow only few pages or logged in users
        if (data.req.loggedIn || allowedPages.test(req.url)) {
                return data;
        }

        # else redirect to /login.
        winston.verbose("[plugin-nodebb-private-forum] User is NOT logged or URL is NOT allowed.");
        return Helpers.notAllowed(data.req, data.res);
};

module.exports = plugin;

I can't see any of the debug log messages containing accessed URL

@julian ok, I was thinking that the nbbpm was here for that!
Thank you for your answer!

Do you know why there is still this message?

package.json

  "nbbpm": {
    "compatibility": "^1.11.2"
  }

The plugin is now live on npm and should be automatically updated when I create a new release version on GitHub.

Thank you again, now it seems to work well!

Can you review the code and maybe test the module?
I would like to be sure that I have not forgot something.

https://github.com/LM1LC3N7/nodebb-plugin-private-forum