[Question] Wird problem with my plugin.
-
@alfw said:
Can it be a other plugin that might be a 1.0.0 plugin that is breaking this ? I sew over the installed plugins that it had those addons installed as 1.0.0 and not 0.9.3:
- nodebb-plugin-composer-default
- nodebb-plugin-markdown
- nodebb-plugin-emoji-extended
These are the default plugins for NodeBB. If the compatibility for these plugins is set as 1.0.0, then you are using the master branch (development branch) of NodeBB and not the stable release (0.9.3).
-
Forum we are talked about are hosted by nodebb.org and after upgrade to 0.9.3 they installed nodebb-plugin-composer-default 3.0.3, nodebb-plugin-markdown 4.0.16 and nodebb-plugin-emoji-extended 0.5.0 . Witch those versions are 1.0.0. Can those be one of the reasons for my plugin for not working or is ther a way for me to debug this on where it's failing?
-
@alfw try this with your plugin...
change this line to use
acpScriptsinstead ofscriptsnodebb-plugin-sso-beam/plugin.json at master · alfw/nodebb-plugin-sso-beam
Contribute to alfw/nodebb-plugin-sso-beam development by creating an account on GitHub.
GitHub (github.com)
don't forget to restart nodebb after the change
-
@pichalite the ACP status shows the NodeBB version as 0.9.3 for master branch too. you might be confused by that.
-
On the dashboard the MongoDB one says NodeBB v0.9.3. and not 1.0.0, but somehow it installed 1.0.0 plugins at that time.
So im pritty sure it also dosent haveacpScripts. And since it's hosted by nodebb.org. It's pritty hard to upadte the plugin whiout waiting for the plugin list to update. -
@alfw as I said in my previous comment, the master branch will display the version as 0.9.3 even though it has updates for next version (has something to do with the nodebb package manager compatibility). I am pretty sure you are using the master branch.
Im helping