@Rome-Li what problems are you facing? I haven't tested the plugin but, the more information you can give here on the community, the more likely you can get help here.
@Alex said:
I will edit the plugins locally then until the plugins's authors put the modification. Thank you @julian for this quick fix. @a_5mith could you let us know when you have pushed it to npm or github please?
Yeah sure.
I believe this is possible with some minor theme changes.
Prior discussion:
https://community.nodebb.org/topic/12751/topic-voting-like-adult-swim-boards-had/11
I correctly assumed (and this has been validated through actual plugin upgrades) that the latest hash in npm points to the most recently published version, and not the highest version.
That is, given your plugin nodebb-plugin-example
If v1.0.0 is compatible with v0.5.4
If v1.1.0 is compatible only with v0.6.0
The latter is published first
A user typing npm install nodebb-plugin-example will receive v1.0.0 of the plugin, irrespective of what NodeBB version he/she is running, even though v1.1.0 is technically newer
Now, special note: The NodeBB Package Manager doesn't do this. When the ACP calls nbbpm to request a suggested package, we query npm for the plugin data, and sort the versions before checking compatibility, so this issue is moot.
