Posts made by PitaJ

@krptg0 what version of persona are you on?

@krptg0 did you just upgrade to 1.11.1? Did that fix the issue?

@krptg0 latest version is 1.11.1 I believe.

Just FYI, pretty sure you can use async.filter for this.

@navid-sassan you need to call eachCallback no matter what, otherwise it will hang.

async.each(groups, function(element, eachCallback) { 
  if (element.name.match('privileges')) {
    eachCallback();
    return; // only exits this callback function, skips the ownership check
  }
  Groups.ownership.isOwner(uid, element.name, function(err, isOwnerBool) {
    if (isOwnerBool) {
      renderData.groups.push(element) 
      log(`element.name: ${element.name}`)
    }
    eachCallback(err)
  }),
}

@Michael-Pfaff can you provide your config.json?

You should be able to apt remove nodejs

@Michael-Pfaff you might have problems with Node 11, I recommend Node 10 for now.

You do realize how crazy old Node 0.10 is, right? It's from 2015. The current LTS is Node 10, the latest version is Node 11.

Odds are that you have nodejs from the main apt repositories of your distro, and node from nvm or something.

@squre said in Fresh install of NodeBB 1.11.1 on Debian GNU/Linux 9 (stretch) issues:

@PitaJ thank you very much for the reply!

1.) Can you advice me which user should I use to go through the installation process? www-data? root? other?

I suggest creating a new nodebb user with a home directory and installing NodeBB into a folder in nodebb's home directory.

Please don't install or run NodeBB as root.

2.) Does it matter which user runs the command "./nodebb start" after successful setup?

Yes, due to file system ownership and permissions. You should run ./nodebb start as the nodebb user if you follow my previous suggestions.

Does user mentioned in points nr (1) and (2) really matter as the service will be available anyway on http://localhost:4567?

Only in the "don't use root" sense. Otherwise it doesn't really matter.

You can check what is available by checking the api route for whatever page the widget will be on. For instance, for the category page, you can visit /api/categories to see what is available.

@youhosi only if the user data is provided in the template context

What's the content of the extensions field? Take a screenshot if you can

I recommend two things:

• Use the Ubuntu installation docs, they're the most maintained. It's essentially the same as Debian
• Use Node 10

Nothing should be owned by root. NodeBB should not be installed or run as root. You should change all of the permissions with chown -r

I was at one point working on a plugin for customizing translations and templates, I've been meaning to pick it back up and finish it, as it's a useful feature.

I know some forums maintain a single plugin for all of the customizations they need: translations, styles, templates, scripts, etc

The best way is to create a plugin overriding the main translations. You just create a new json file in the plugin languages folder and it will be merged on top of the core translations. This might be helpful:

https://community.nodebb.org/post/44253

You can actually override plugin translations as well as long as your plugins are loaded in the correct order.

You're probably better off adding a custom class to the navigation item and then using the custom js in the acp for the rest

@faizanzahid the current version of NodeBB still has compatibility with those plugins. Future version will not.