How the hell do I get the settings for the plugin

PitaJ

Check out the following examples:

Edit: Widget settings are passed into the widget render function I think

PitaJ

Widget examples: https://github.com/NodeBB/nodebb-widget-essentials/blob/master/library.js

Mikael Jenkler

Yeah, i know I can get them from render. But i need them in static app load.

Mikael Jenkler

Do you know if I can get the widget data from meta.settings ?

PitaJ

Widget settings aren't available through meta.settings. Because you can have:

multiple templates with the same widget
multiple widget areas per template
multiple instances of the same widget per widget area

What are you trying to accomplish?

Mikael Jenkler

let test = meta.settings.get('nodebb-widget-rss', (err, data) => { if (err) { callback(err); return; }});
console.log(test);

Tried this, no data.

I am running function that runs itself in some intervall and need to be able to get updated widget settings if it changes in the acp without restarting nodebb.

I know i can get it from render but then it will be dependent on a user visiting the page where the widget is. There must be a way to fetch widget settings at startup and in runtime.

PitaJ

@Jenkler like I said, you have to consider a condition where there are multiple instances of the same widget. If you want settings to be shared across widgets, then you'll want to set up an ACP plugin settings page for your widget, and configure global settings there.

Mikael Jenkler

@PitaJ ahh, now I get it, of cause. So widget data is only available thru render so it is isolated. I guess its good that way. Need to solve it some other way then

Thanks man!

yariplus

You could get the widget settings the same way the admin page does. Make a list of widget areas, then fetch the data for each widget. Then, filter the returned object for the specific widget you're looking for.

Mikael Jenkler

@pitaj did I understand correctly.

Nodebb-plugin use meta.settings.get
Nodebb-widget-* does not have support for meta.settings.get

Nodebb config global is stored in meta.config.* and should only be used for nodebb core? Old plugin used meta.config.* but that the where a prefix on the key value so we know what config is for what plugin

I still use meta.config.* for settings for everything. I only have global configs for my widgets and plugins.

What is the preferred way and why?
Will meta.config.* be deprecated ?

PitaJ

Widgets are just a special kind of plugin. You can use meta.settings.get in widgets if you want, but only if you have a setting that is shared across all widget instances.

I'm not sure what you mean by using meta.config but I don't see anything wrong with it.