plugin load sequence

[xidui]

If I edited a tpl in pluginA and the same tpl in pluginB, which one eventually counts? Can I define such a loading sequence?

[yariplus]

Plugins should not be modifying templates, only themes should be modifying templates.

You should use an exposed hook, define a custom page, or use jQuery to inject your content on the client-side.

How are you editing the templates? What changes are you trying to make?

[xidui]

@yariplus
I made the following plugin: https://github.com/wktang/nodebb-plugin-category-sort-by-votes
It can sort the topics by the votes of their maidPid.
I had to change the sort by panel(add "most_votes" to it). So I had to change the tpl file which arises the issue of loading sequence.

If the tpl in persona-theme loads first, all will be fine. But if the persona-theme loads last, my change in this plugin will be overlapped.

[xidui]

@yariplus
I am lucky that my plugin loads after the "persona" theme. So it works fine.
But I think lucky should not solve all kinds of problems.

[yariplus]

Instead of replacing the template like you are doing, make your changes to the file at runtime, using the emitter event 'nodebb:ready' like here.

Rename your template to sort-by-votes.tpl so that the original isn't replaced, and only put your changes inside. When the ready event happens, modify the original template by adding your changes to it with a replace(). Like shown here.

[pichalite]

@xidui yes, you can order the plugins. On ACP -> Extend -> Plugins page there is a "Order Active Plugins" button.

[yariplus]

Here's a regex you can use for my method above.

Edit fiddle - JSFiddle - Code Playground

Test your JavaScript, CSS, HTML or CoffeeScript online with JSFiddle code editor.

(jsfiddle.net)

[xidui]

@yariplus
thanks, I will have a try

[xidui]

@pichalite
Oh~ thank you

[exodo]

@pichalite said in plugin load sequence:

@xidui yes, you can order the plugins. On ACP -> Extend -> Plugins page there is a "Order Active Plugins"

That doesnt solve anything most of cases

[pichalite]

@exodo explain?

[exodo]

@pichalite said in plugin load sequence:

@exodo explain?

If a plugin is slow it wont solve to put it first. It will still finish last. Happened to me with many plugins

[yariplus]

I was wondering about that, the plugins load asynchronously it seems, so what does the order even do?

[pichalite]

@yariplus hmm I didn't look at the code I just thought it worked that way based on what I read here when this was implemented.

[pichalite]

based on this... looks like they are loaded in order one after the other...

File not found · NodeBB/NodeBB

Node.js based forum software built for the modern web - File not found · NodeBB/NodeBB

GitHub (github.com)

[yariplus]

@pichalite That makes sense, but the app.load hook is still called asynchronous. (each instead of eachSeries)

https://github.com/NodeBB/NodeBB/blob/master/src/plugins/hooks.js#L169

So there is no way to tell if another plugin has finished loading yet.

[yariplus]

This topic is deceiving though. The plugin load order has nothing to do with the issue. Like I said in my first post,

Plugins should not be replacing default templates, period.

It is ugly, not guaranteed to work, and breaks every other plugin that attempts to do the same.

I already suggested a more sensible system here.

Template placeholders. · Issue #4728 · NodeBB/NodeBB

A few plugins modify templates at load or require manually editing templates. This works most of time, but is dependent on the theme and prone to breakage. If we could add template placeholders to themes that were filled in by NodeBB, it...

GitHub (github.com)

[pichalite]

@yariplus so, the plugins are registering for the hooks in order but when the hook is fired, they run asynchronously?

[yariplus]

@pichalite That seems to me to be the case.

[julian]

@yariplus said in plugin load sequence:

@pichalite That seems to me to be the case.

However, the code does not agree -- they are run in series.

They do time out for performance reasons, however. e.g. a static hook will continue with the next listener if the current one takes longer than 2 seconds.