Topics created by Dravere

@jtsimoes Yes, you could call it an e-mail blacklist.

@Dravere Yeah I meant in code, would need to comment out the lines that match new cron

I'd like to do the same. For instance, some folks don't like round avatars, so I would override the CSS for that. Other folks want zero color, so I'd make a monochrome skin.

Oh, we are actually supposed to be merging the version bump back into master, let me do that now.

I just release version 0.3.0 of this plugin. The following changes have been implemented:

Using action:analytics.increment for analytics counter (better performance and accuracy) Added label viewer to page view that can have the values user, guest, or bot (inspired by an upcoming change in 1.11, you get it early here) Added new metric nodebb_online_guests Added new metric nodebb_eventloop_lag_seconds. This is measured by NodeBB which has a smoothing factored compared to what is measured by NodeJS and provided via nodejs_eventloop_lag_seconds Added new metric nodebb_eventloop_maxlag_seconds. This is the maximum allowed lag for NodeBB. If the lag is getting closer to this value NodeBB will start to issue 503 error codes. The chance a user is getting a 503 is calculate by this formula: (lag - maxLage) / maxLag.

@Per0x Sorry it took a while but your metric for online guests is now finally available.

👏

The "top downloads" pie chart is a little misleading, actually. The package manager itself doesn't have any visibility on package downloads because those are done through npm, and not nbbpm itself. What it does track is how many people ask nbbpm to suggest a version to download.

For example, if you run v1.8.1 and you want to download a plugin, the latest version might not be compatible, so the ACP will query nbbpm for a suggested version. That's counted as a "download" (since the "suggest" call is done behind the scenes and is opaque to the end user).

So you could be seeing true downloads... people downloading your plugins... or someone's just hammering GET /api/v1/suggest?package=nodebb-plugin-prometheus a lot 😄

@dravere I think the bug only happened if the user's system time was off.

There is the traffic management settings and the option to set the threshold for the event loop lag. Under the value you can set there is a short help text that confuses me a bit:

Lowering this value decreases wait times for page loads, but will also show the "excessive load" message to more users.

Why does lowering of this value decrease wait times for page loads? I went through the code and I didn't feel like this value would change anything in regards to the page load time. What am I missing?

@dravere said in Is there a way to display moderator rights only in category the user is a moderator?:

Otherwise I think it could be done via the hook filter:topics.addPostData? Just iterate over the posts array, get the category, and for every user of a post add an object to custom_profile_info with the property content set to some HTML indicating moderator rights?

Probably this... alternatively, use the groups method, but hook into filter:topics.addPostData to remove the group badge if they're not in the category that user moderates?

👏 Well done, that's some thorough investigating @Dravere !

Would you like us to fire an action hook when static:app.init has finished executing?

Thank you. Will have a look at it. Probably will use that plugin for some other stuff anyway so it is a great additional use for it 🙂

I think I'll mark this topic as answered.

i agree with u and need something similar.

It seems that there is still the possibility to upload a profile cover picture, even though I disable "upload images" in privileges for registered users.

Again, thank you for the prompt answer!

@Dravere I tried this but it didn't seem to resolve the problem for me. I don't have the sites in sub-folders - I'm using different ports instead i.e 4567 and 4566

I added the code here:

https://github.com/NodeBB/NodeBB/pull/4663/commits/b530361851c45311e98b76759710216d595d22eb

Dravere created this issue in NodeBB/NodeBB closed Made the session cookie aware of the possible relative path #4663

Well, after that post I went digging in the code. And look what I found:
https://github.com/NodeBB/nodebb-plugin-composer-default/issues/37
https://github.com/NodeBB/NodeBB/pull/4621

That actually fixes my issues. I updated to weekly and everything seems to work nicely. Seems to have also fixed the problem with the websockets. I see no more errors. When can we expect the v1.0.4? 🙂

AdJones created this issue in NodeBB/nodebb-plugin-composer-default closed Errors when using NodeBB in a subfolder with latest version #37 AdJones created this issue in NodeBB/NodeBB closed Fixing issue where the relative path was ignored for express modules #4621