problem on install plugin

NodeBB Plugins

Suggested Topics


  • Remove plugin from nbbpm

    Solved NodeBB Plugins
    0 Votes
    1 Posts
    177 Views

    Hi, I have package/plugin in nbbpm

    nodebb-plugin-change-reputation-test

    how to remove it?
    (I already removed it from npm)
    Thanks

    Thanks @administrators for the removed 👍

  • 0 Votes
    1 Posts
    262 Views

    can't install this plugin in my admin portal

    when i install it theres a pop up error like this

    gyp\lib\configure.js:509:16) gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\polyfills.js:282:31 gyp ERR! stack at FSReqCallback.oncomplete (fs.js:158:21) gyp ERR! System Windows_NT 10.0.15063 gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" gyp ERR! cwd C:\Users\Darrel John Javier\nodebb2\node_modules\contextify gyp ERR! node -v v11.14.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Darrel John Javier\AppData\Roaming\npm-cache_logs\2019-05-08T03_16_30_506Z-debug.log

    somebody help 😞

  • 0 Votes
    5 Posts
    2k Views

    @hearsedriver Glad you figured it out 😄

  • 0 Votes
    6 Posts
    4k Views

    I installed and activated the plugin-sanitizehtml , restarted NodeBB as instructed, saved the default plug-in settings from ACP.
    But, now all my HTML tags have been stripped off (I can tell by looking at the source)
    What am I missing ?
    BTW, I uninstalled the Markdown-plugIn before installing the sanitizehtml plugIn.

  • 0 Votes
    6 Posts
    2k Views

    @pitaj Something to note is that if the plugin has already been required, subsequent requires will still have module.parent pointing to the first module that required it.

    So... when NodeBB starts and it requires plugin-foobar, its module.parent is plugins.js

    Later, if plugin-barbaz requires plugin-foobar, its module.parent stays as plugins.js.

    So if you only require the module after NodeBB is done with it (e.g. defer requiring until it is actually required), you might be ok.