@julian said in Which is better NodeBB or Discourse?:

@Joykiller said in Which is better NodeBB or Discourse?:

I look at it from another point of view..
NodeBB is more of a developer board and Discourse is popular and has more developers for consumer usage. Nodebb just isn't user friendly enough for changes for users just my 2cents.

Yes, that is the sad reality of it, is that we're not as large as Discourse nor do we have as much money, but I still feel we've come up with a competitive product that holds a candle to it.

The unfortunate part is that that last 10% to even out the rough edges requires money, or developers, and often both, and while we're around, many thing pull at us in many different directions

Seems to be an issue with many open source products in general...

Yep, Nodebb is great problem with it getting more people to use it is tied directly with the type of plugins/features available to users. Have you got statistics data on the type of person who uses this board of is it varied? I my self use mostly for gaming communities. So things like Discord/Steam integrations are hugely popular things. - Just a thought of focusing on the groups and making some popular plugins for attracting those users may help. I personally hate Discourse due to their docker wrapper. but thats me.

@baris said in Plugin Dev [newb Question]:

Depending on which template you want to add it to you can use it's build hook. If it's topic.tpl then you can use filter:topic.build, Here is a sample.

myPlugin.filterTopicBuild = function (hookData, callback) {
  const uids = hookData.templateData.posts.map(p => p.uid);
  user.getUsersFields(uids, ['valueId'], function (err, valueData) {
    if (err) { return callback(err); }
    hookData.templateData.posts.forEach(function (p, index) {
       if (p) {
           p.valueId = valueData[index];
       }
    });
    callback(null, hookData);
  });
};

This code would make the valueId field available to the template topic.tpl so you can use it with {posts.user.valueId}

Thank you! - I'll get to playing around with this soon. GoT finale and all ha.

Oh question, what if the tpl is custom? Do I need to do anything diffrent than above other than changing the tpl file name?
Well anyrate ill ask stuff once i play with it for a bit. Thx again.

Ok, So I have figured out the template system, learned from some other plugins a few things. Able to modify broken ones to make work again etc.

Now I have a plugin that on their registration adds a field to their main user mongo objectid. Question is where can I find some useful information on how to pull that said information from the database to display it in html on the template.

I know base values can be done such as username etc with {username} obviously I need the plugin to "whitelist" or add this new value to be able to use it in templates too.

I'm self taught programmer, learn from things i see. Examples are super helpful to me.

I assume id have to do something like:

Require User src
User.getUserField(data.uid, 'NAMEOFID', function (err, NAMEOFIDDATA) {
 //What to do here to push it to template field?
}

I just find it hard to find accurate documentation and descriptions of nodebb plugin making maybe im looking in the wrong areas but seems like its hidden easter eggs.

But yeah, a bit more detail.

db.objects.find({_key: "user:4"})

{ "_id" : ObjectId("5ce1e1fa549c71c7acd236cb"), "_key" : "user:4", "valueId" : "hello", "returnTo" : "/" }

(Obviously theres more in that object id i just removed it) - however I want to display valueid's value (hello) to a tpl. If this makes it easier to understand.

@julian said in [nodebb-plugin-ns-custom-fields] NS Custom Fields:

@Nicolas @Joykiller Ah yeah, write API listens for some hooks if you want to add your own routes to the Write API

Seems a little redundant because you could just attach the route to app yourself in your init handler, but... well, there it is.

Yeah decided to just write directly to mongo for what i need.

@julian said in Which is better NodeBB or Discourse?:

Hm... I made the conscious decision to develop the Write API separately mostly because it's not a feature that many people use. Those admins who want deeper integration would, certainly, but I think at the time, I wasn't entirely sure how much it'd bulk up the codebase were I to build it into core itself.

That said, I try to keep on top of it in terms of compatibility... and the Write API's RESTful interface is much more organized than NodeBB's read API, simply because it was designed that way, instead of organically grown. Was there anything specific you wanted me to address in the Write API?

With regards to documentation, I realize we really need some sort of auto-generated doc tool to show API responses. Having to "code it first and see what the responses are" should not be the way to develop...

So many things on our backlog

I'm sure we all understand the effort you guys put in everyday. Just do what you can, I've noticed many "newer" more modern forums such as Discourse for example utilize some type of built in API system for integrations. Basically would love to see an API for read/write built into the core.

Pre-context: I been a user of Nodebb for a while, I waited like 2 years and came back still not much in terms of average user QOL changes. Not saying you guys havnt done anything im sure theres lots of core fixes and so forth let me explain in more detail below.

A bunch of small QOL changes would be nice to see as well, at least from the small time that I've started back into Nodebb development for a project i'm working on. I've had to custom build some plugins just to modify things that should be also written into the core system. It's kind of out of reach for your average person cant expect them to write plugins to fix specific things like these.

Example: GDPR modifying the text would require a plugin to modify the lang output. Would be nice where in the settings section where you can enable / disable to modify that with a modal popup etc. I'm sure theres others but this is only from what ive came across.

But I love nodebb. AS in terms of this thread "Which is better?"

I look at it from another point of view..
NodeBB is more of a developer board and Discourse is popular and has more developers for consumer usage. Nodebb just isn't user friendly enough for changes for users just my 2cents.

When registering the users get:

This community forum collects and processes your personal information.......

Just was wondering how to modify this properly is there a way in the backend on admin section? Tried to find it in search but not entirely sure what to keyword search for lol. I searched the backend and lang file found it under user.json.

I assume theres no way in the backend to modify this file. Except writing a plugin?

(Guess I answered my own question..) However, you should probably look at adding a popup modal or something to modify the GDPR for users in ACP. Which would overwrite it and save.

Thankfully not to hard to update, just json in the right directory path with the same name to update/writeover the fields.

@scottalanmiller Yeah, im in the middle of writing a system that would love to utilize the API, but the write API and having to manually update other plugins for their routes and all that, along with trying to figure out peoples coding stack is too much. So I'm prob just going to end up writing/searching the mongodb instead. But API would be awesome.

@scottalanmiller said in Which is better NodeBB or Discourse?:

I do wish that a few more things in NodeBB were built in rather than plugins. Not a lot, just a few.

Yep like API access to everything. IMO that's huge for customization for various things. (I'm bias because i need all the api's i can get my hands on.)

@Nicolas said in [nodebb-plugin-ns-custom-fields] NS Custom Fields:

Version 6.0.0

The new version is available. Summary: no new features.

• Changed compatibility with NodeBB v1.11.x

Does this plugin work with write api? if so what would be the data to post to modify? Because; _uid=2&steamid=test or _uid=2&customFields[0].steamid=test"

The key doesnt seem to work.

So I was looking into it, basically need to add routes etc, your code base is deeply confusing to me. So I'll just request and hopefully in the future youll add it

@Nicolas Can you please add custom fields routes to allow access via nodebb write api pretty please

@PitaJ said in Private Git for install plugins:

@Joykiller there's no easy way to keep the links with npm, but yarn is better at not killing them.

Ah ok, well ill put up with it. Till I write some bash that checks to make sure the links there or something and if not replaces it after some trigger. I'll look into it later.