Im going to have to do some f*kery on this. Let the hacks begin

@PitaJ Yes exactly!... I had to write a small tweak inside: nodebb/public/src/modules/alerts.js

    (ajaxify.data.template.categories) && ($('[component="topic/purge"]').length === 0) ? 
     null : 
     createNew(params); 

This does not fix the reason why users who are not admin or moderator are getting this error each time they hit the bottom of the topics on the categories page.

This resolves my issue but still dont know why it would keep popping this error. When the user is admin it will not appear. But regardless, it should not keep firing this if the user is just a regular user and scrolling to the bottom of the group they are a member.

@PitaJ When I filter out the posts that do not belong to the group .... I am left with a smaller amount of posts... I need to get more posts to fill the page.

When the page renders the posts in the group... I am filtering out all of the member posts that do not belong to that group.... NodeBB appears to provide the last 10 posts from the members that are part of that group.

If the top 10 that are coming back have for example 8 of them that posts from a different group ... I am filtering them out.. I dont want to see them since they are not from the group the user is currently viewing.

When I do this, I only have 2 remaining that are associated to the group that the user is viewing. I need to now figure out how I can get another 8 of them that do belong to the group that they are viewing.

Hope this makes things a bit clearer.

NodeBB for whatever reason is showing both the posts made inside the group being viewed by the member but also the posts the member made in other groups.

I dont want to show any of the posts made by the members from other groups. I only want to show the posts made inside the actual group being viewed. My filter is removing those posts made in outside groups by these members. When I filter I am left with a small remaining amount to show on the template.

I was able to hook into the

filter:groups/details.build

And do something simple to filter like this:

plugin.groupDetail = function(data,callback){
	let f = data.templateData.posts.filter(p=>data.templateData.group.name === p.category.name);
	data.templateData.posts = f;
	callback(null,data);
}

The result was that it limited the results on the group details to only reflect the posts that match the category. However, I then will need to requery the database and re-render the data and re-generate new objects to get more posts that belong only to this specific category.

All I simply want to do is make the group details only show the posts that belong to that specific group. Currently the nodeBB is showing all of the posts that a member of the group has made even when the posts could be from a totally different group.

Any suggestions or advice, greatly appreciated. I am trying to avoid making changes to nodebb base and do all of this from my plugin.

When the user scrolls to the bottom of a category they are a member of they get the error below:

The dev logging shows the following:

verbose: [plugins/fireHook] {"meta":"filter:privileges.categories.get"}

Inside the ACP > Privileges for this specific category I have a group assigned and members of this group has full access to all of the permissions for this associated category.

Why is this message coming up?

Any ideas?

Thanks!

It appears that if you have long thread and you use back navigation on browser it highlights to show you the last post you clicked.

What does this highlight mean ? Sometimes when I load a category the page will highlight a topic with a blue background... I want to know what this is used for. I want to disable this functionality.

I'm trying to catch the css class that is getting adjusted on the DOM, but its going quick and I am having trouble locating it.

UPDATE: the class appears to be called .highlight

RESOLVED

If anyone else sees this thread... Don't be the american who thinks the default should be en-US....

It appears that the nodeBB default language was set for en-GB

If you need to adjust the language default setting:

Go to your NodeBB ACP (admin control panel) => General => Languages

I might have found the issue....

I see that my nodebb is defaulted to en-GB

Let me switch this! One moment....

I am using grunt for development, but i have fully killed the grunt watcher and have manually started up the ./nodebb build and made sure to fully kill and start up nodebb so it rebuilds all assets.... Still Its not using the language file.

Where can I check the default nodebb language setting that is currently in use?