I guess preload hook is what I needed:

plugin.preload = function (params, callback) {

    params.app.get('/', function (req, res, next) {
        if (req.query.ad) {
            res.send('Hiii')
        } else {
            next()
        }
    })

    callback()
}

So I want to do this:

1. If someone opens www.myhomepage.com, then he will be redirected to the forum
2. If someone opens www.myhomepage.com?page=lol.html then he will be redirected to my custom lol.html page

I'm aware that I can create a custom route from my plugin, but this is not what I want.

I'm currently using the following hooks:

"hooks": [
    {
        "hook": "static:app.load",
        "method": "init"
    },
    {
        "hook": "action:post.save",
        "method": "postSaved"
    },
    {
        "hook": "filter:post.create",
        "method": "postCreated"
    },
    {
        "hook": "filter:topic.create",
        "method": "topicCreated"
    }
]

I tried using helpers.setupPageRoute on / but it simply doesn't work, probably because the route is being processed before the plugin routes are added.

Is it possible to achieve what I want?

@baris Indeed, I was logged with admin account. I tried with a regular user and it works correctly. The "Upload Image" button does not show and uploading with CTRL+V gives me the following error:

Thanks for clarifying and sorry for the misunderstanding.

I'm on NodeBB 1.9.1. This is my ACP:

And this is how a reply looks:

Despite disabling uploads everywhere, I can still CTRL+V a picture saved in the clipboard or manually click the "Upload Image" button.

Is there another setting that I'm missing that disables completely all uploads?

I suppose the setting that I'm referring to is located in loader.js:

var logrotate = require('logrotate-stream');
...
var outputLogFilePath = path.join(__dirname, 'logs/output.log');
var output = logrotate({ file: outputLogFilePath, size: '1m', keep: 3, compress: true });

It would be nice if we could customize these parameters.

These are the contents of my logs folder:

[ec2-user@ip-XX-XX-XX-XX logs]$ ls
output.log  output.log.0.gz  output.log.1.gz  webinstall.log

This gives me about 2h30-3h of server logs so any errors that occurred before this interval are lost. I'm running NodeBB 1.9.1 and I have a custom NodeBB plugin that runs some stuff. It is responsible for most of the logging as well as the crashes that I'm currently experiencing.

How can I make NodeBB to create more log files, i.e., output.log.2.gz, output.log.3.gz, etc?

Awesome! It worked for me and indeed, there's no delay. Also, to hide the views in the post bar, I used this one:

.topic-main-buttons .stats:nth-child(3) * {
  /* to maintain formatting */
  visibility: hidden;

  /* to hide completely instead */
  /*display: none;*/
}

Thanks a lot!

It may sound strange to hide this stat, but it is useful for my use case. I'm mainly looking to hide the following:

I searched these forums and couldn't find anything related. It seems to be only doable through a plugin. I attempted using the following script in "Custom Header", but it doesn't work properly because of asynchronous stat loading:

<script>
$(document).ready(function(){
    $('div.stats.hidden-xs').each(function(i){
        var divObj = $(this)
        divObj.find('small').each(function(j){
            if($(this).text() == 'Views'){
                divObj.hide()
            }
        })
    })
})
</script>

When you first load a page, the views are shown. If you refresh it, the views get hidden the way I want.

Thanks for your attention.

I asked one of my moderators with UID > 213 and he was seeing the categories just fine, even after removing him from Global Moderators. Only my moderator account with UID = 2 that is experiencing this issue.

With that said, I suppose it's definitely a DB upgrade conflict.

I think the problem has something to do with old accounts becoming Global Moderators. This is my DB with 261 registered users after querying {_key: /group:registered-users:members/}:

For those 4 Global Moderators:
3 of them have UIDs > 213
1 of them has UID = 2

The one with UID = 2 is the non-admin account that I was using to test in my previous post. I then made another newly created account a Global Moderator, kicked him from the group and the categories appeared just fine.

I've been upgrading my database since NodeBB 0.7.0 and I'm starting to believe that the issue is due to some conflict with old accounts. In any case, I will do some more testing to confirm my theory. I will ask one of my moderators (UID > 213) to login and see if he can see the categories or not.