Plugin Development

@julian Sorry, hadn't seen that you hadn't got a private npm account to play around with!

@psychobunny That's a really good idea, it's actually how I've been testing separate projects that use my privately hosted modules currently, before publishing the updates to the npm account.

It would be great if support came out the box at some point though 🙂

Yepp.. I convert it back after parsing manipulating the url.

@pitaj
Boy, that was quick! Thanks 🙂

Created a small plugin, to have access to all groups - https://community.nodebb.org/topic/4591/nodebb-plugin-ns-api-ns-api-extended

Ok, question is closed 😉
I have created plugin for my needs

Now it works! @psychobunny plz check it out and do a code review if you have the time 😉

Thanks a lot. This should save me loads of time! 🙂

Hmm. That might make sense, maybe on plugin activate it appends to end and on deactivate it removes it

That's in my area, PM me details maybe I'll come swing by

meta.config contains settings from NodeBB itself. Plugins retrieve their own settings via the settings module on the client side.

In the case of quickstart, you can retrieve the settings the same way the settings are retrieved in the plugin's ACP page, with Settings.load

@pichalite try this 😄

Link Preview Image Dropbox error - 'echo 100000 | sudo tee / proc/sys/fs/inotify/max_user_watches'

Dropbox gives me an error that mentions echo tee 100000 but then it disappears. How to fix or remove msg?

favicon

Ask Ubuntu (askubuntu.com)

See: https://github.com/kurt-stolle/nodebb-plugin-exclserver/blob/master/templates/exclserver/servers.tpl

Why does the <script> tag sometimes not load after rendering the page?

Hello,

How to use action:auth.overrideLogin hook? what arguments are needed (or at least where to find such information)?
Assume we have function magic() which performs authentication. How would the rest of code look like? How to obtain credentials?

Any help highly appreciated 🙂

I will need upload functional in future plugin.
Is there any Upload API already in NodeBB ready for plugins use?
I would like to use ready to use solution, if any, before I will do it myself 😉

My case is to provide text-area for the user in ACP, so user for example can "change template" of rendering list item.

For example one possible solution:

Store template markup in settings, and ask user to reload NodeBB. In static:load use file system instruments to rewrite template.

But I'm not happy with such solution 😉

Good news, that we don't need to add filter, there is filter for user profile: filter:user.account
But what is about static template?

Same problem again...

Actions that I have made to 'fix' this problem:

Disable single plugin ./nodebb reset plugin="nodebb-widget-essentials" - No Success Disable all plugins - No Success Drop all collections in Mongo, and ./nodebb setup - No Success Delete nodebb.min.js from public directory - No Success Delete all public subdirectories that could be found in .gitignore - No Success Delete public directory and checkout latest from current branch - Success

Maybe it will give you some insights 😉

Inside of the client script... Anyway, I just restarted NodeBB and tried it again, it works fine now 🙂 Thank you!

@psychobunny is there any option to include plugin client js only for /account/edit endpoint?

Also, Do you have an ideas, how to augment template for the plugin use - templates/account/edit.tpl? I need add dynamic set of fields to the template, Vanilla's account-edit template is 3 column layout (md:2-5-5), I would like to have (md: 2:4:3:3). Main problem here, that I can't find really abstract approach, solution will be very dependent on Theme... One solution, just replace template on app startup, another option, create set of regexps and try to change template or dom manipulation to get another set of columns. Anyway I'm looking for less dependent solution, so It will not brake with every release of the theme and easily work with another themes

Taking everything into consideration, I will swap edit.tpl and include client js with a template just as script tag. But maybe you have better ideas 😉

That error is caused by the following bit of code in src/plugins.js

paths = paths.map(function(pluginLib) { var parent = path.dirname(pluginLib); return cached.filter(function(libPath) { return libPath.indexOf(parent) !== -1; }); }).reduce(function(prev, cur) { return prev.concat(cur); });

If paths is an empty array calling reduce will throw that error. We should add better checks to detect that.