How to retire a plugin?

NodeBB Plugins
  • I had 2 plugins that have now had core features merged into the official versions they were forked from.
    My repos now serve no purpose, they will break over time, they are useless now and shouldn't be used.

    How do I get them off the package list?

  • If you've set a strict nbbpm-compatibility the plugin shouldn't get listed in versions not matched as far I know.

    Additionally you could deprecate your npm package in order to make it clear that it's out of purpose these days.
    This way you're doing the best you can (and should) to state it.

    I don't know if the NBBPM checks deprecations thought.
    But if it does since it's not a new publish you may have to manually PUT your plugin to trigger the update - I don't know whats included within the update-list the NBBPM checks regularly.

    If it's not getting noticed by the NBBPM it probably should, ping the devs then.

    reference where to find how to PUT the NBBPM:

  • The nbbpm checks new packages that get added to npm, so if you unpublish your package, we won't know.

    Best bet would be to keep the package there so users on old NodeBB versions can still install it, but put an nbbpm.indexed = false in package.json, so when it comes through from npm, nbbpm will know to remove it from the index.

Suggested Topics

  • 1 Votes
    1 Posts

    I'm using nodebb-plugin-ns-custom-fields plugin. but it seems not working.I wasn't found the setting page in my acp panel. Does anyone know how to fix this problem or some alternative plugins to add custom fields in user's profile

  • 3 Votes
    6 Posts

    @pwFoo there was a bug in a code.

    Please, update plugin to the last version (0.3.6), change again the lines 60, 61 and 65 of library.js, reload, restart and test again. Sorry for the inconvenience

  • 0 Votes
    8 Posts
    root@community:/var/nodebb# systemctl stop nodebb root@community:/var/nodebb# ./nodebb build started 2018-06-07T16:34:56.255Z [7073] - warn: You have no mongo username/password setup! 2018-06-07T16:34:56.747Z [7073] - info: [build] Building in parallel mode 2018-06-07T16:34:56.748Z [7073] - info: [build] plugin static dirs build started 2018-06-07T16:34:56.751Z [7073] - info: [build] requirejs modules build started 2018-06-07T16:34:56.752Z [7073] - info: [build] client js bundle build started 2018-06-07T16:34:56.754Z [7073] - info: [build] admin js bundle build started 2018-06-07T16:34:56.754Z [7073] - info: [build] client side styles build started 2018-06-07T16:34:56.755Z [7073] - info: [build] admin control panel styles build started 2018-06-07T16:34:56.756Z [7073] - info: [build] templates build started 2018-06-07T16:34:56.757Z [7073] - info: [build] languages build started 2018-06-07T16:34:56.757Z [7073] - info: [build] sounds build started 2018-06-07T16:34:57.113Z [7073] - info: [build] sounds build completed in 0.356sec 2018-06-07T16:34:57.268Z [7073] - info: [build] plugin static dirs build completed in 0.52sec 2018-06-07T16:35:00.633Z [7073] - info: [build] client js bundle build completed in 3.881sec 2018-06-07T16:35:00.634Z [7073] - info: [build] admin js bundle build completed in 3.88sec 2018-06-07T16:35:00.758Z [7073] - info: [build] languages build completed in 4.001sec 2018-06-07T16:35:00.761Z [7073] - info: [build] templates build completed in 4.005sec 2018-06-07T16:35:00.930Z [7073] - info: [build] client side styles build completed in 4.176sec 2018-06-07T16:35:01.997Z [7073] - info: [build] requirejs modules build completed in 5.246sec 2018-06-07T16:35:02.096Z [7073] - info: [build] admin control panel styles build completed in 5.341sec 2018-06-07T16:35:02.097Z [7073] - info: [build] Asset compilation successful. Completed in 5.35sec. root@community:/var/nodebb# systemctl start nodebb
  • 4 Votes
    21 Posts

    Most likely the theme will need some integration before subcategories will be shown. At present, I believe only vanilla and lavender show subcategories.

  • 5 Votes
    66 Posts

    @julian @a_5mith and this only happening when i use the code from below, when i switch back
    everything works as a charm.

    (function(module) { "use strict"; var YoutubeLite = {}, embed = '<div class="js-lazyYT" data-youtube-id="$1" data-width="800" data-height="450"><iframe class="lazytube" src="//$1"></iframe></div>'; var regularUrl = /<a href="(?:https?:\/\/)?(?:www\.)?(?:youtube\.com)\/(?:watch\?v=)(.+)">.+<\/a>/g; var shortUrl = /<a href="(?:https?:\/\/)?(?:www\.)?(?:youtu\.be)\/(.+)">.+<\/a>/g; var embedUrl = /<a href="(?:https?:\/\/)?(?:www\.)\/embed\/([\w\-_]+)">.+<\/a>/; YoutubeLite.parse = function(data, callback) { if (!data || !data.postData || !data.postData.content) { return callback(null, data); } if (data.postData.content.match(embedUrl)) { data.postData.content = data.postData.content.replace(embedUrl, embed); } if (data.postData.content.match(regularUrl)) { data.postData.content = data.postData.content.replace(regularUrl, embed); } if (data.postData.content.match(shortUrl)) { data.postData.content = data.postData.content.replace(shortUrl, embed); } callback(null, data); }; module.exports = YoutubeLite; }(module));