@greenmoon said in Which are your favorite nodeBB plugins?:

is it possible to restrict "canned-responses" to moderators and admins only?

Very late, but I use this JS in my custom header to limit canned responses to admins only

    // Hide canned responses unless you are an admin
    $(window).on('action:composer.loaded', function() {
        if (!app.user.isAdmin) {
            $('.composer [data-format="canned-responses"]').hide();
        }
    });

@julian said in Which are your favorite nodeBB plugins?:

In the newer stable releases of NodeBB, we've actually updated the search so that posts are returned by relevance, instead of by post time, so Solr is even better now

What version of NodeBB did this start in, and does this require Solr?

In the spirit of staying on topic, here are some of my favorite plugins

• Session Sharing
• Q&A
• S3 Uploads
• Slack Integration

@baris Thanks. Will do

I'm using Nodebb's hosted service, and I'd like to test upgrading an identical copy of it locally prior to upgrading to 1.2.0. Can I duplicate the forum (posts, settings, users, and all) and run it locally?

@baris Thanks! You and the rest of the NodeBB team / community rock.

@baris said in Plugin works in development but not in production:

What is not working? Did you try testing with mongodb locally?

Sorry for not being more clear. No reputation is being awarded for each post in production. Reputation is being awarded for each post locally. I haven't tried using mongodb locally, but that's the next step.

@PitaJ said in Plugin works in development but not in production:

@deiden26 without calling the callback, NodeBB had no idea when you've finished your task. So until you call that callback, the value is indeterminate.

Edit: you just need to add the callback parameter to your function, and then add it as an argument to the waterfall.

Are you suggesting that this line

plugin.awardReputation = function(postData)

should have a callback parameter, like this

plugin.awardReputation = function(postData, callback)

and that my waterfall should end in

], callback);

?

That doesn't seem right to me, because the awardReputation function is being called for the action:post.save hook. This hook only provides postData and no callback.

@frissdiegurke said in Plugin works in development but not in production:

I guess he wanted to state that the next callback from line 42 is not called at any time.

Ah. Thank you. Do you think this might cause an issue? I figured that because I am not providing a final callback for async.waterfall the next parameter would probably just be null.

@baris said in Plugin works in development but not in production:

Something looks wrong here https://github.com/myvr/nodebb-plugin-reputation-for-posting/blob/master/library.js#L42-L45. checkConditionAndRewardUser does not send back a callback

Could you explain a bit more about what seems off? From what I can see, checkConditionAndRewardUser takes an optional callback parameter, but I'm not providing one because this is the last task in the waterfall. If you are referring the the callback parameter the the anonomous function I send for the method parameter of checkConditionAndRewardUser, this should be filled by the checkCondition method that checkConditionAndRewardUser calls with its method parameter as an input. Wow, that's a mouth full

First of all, use your own version of the async library. It's bad practice to depend on someone else's dependencies. So replace module.parent.require('async'); with require('async');.

Thanks. Will do

Make sure your local and server instances are on the same commit.

Definitely on the same commit.

Check for any errors in the logs.

Done. I didn't see any issues

I just made a shiny new plugin to award reputation to users for every post. The plugin, however, is only working in a local instance of NodeBB. It is not working in my production instance. The only notable difference between the two is that the local instance is using a redis database while the production instance is using a mongo database.

Does anyone know what might be causing this?

https://github.com/myvr/nodebb-plugin-reputation-for-posting

I would also be interested in this feature

@yariplus My mistake. I was confusing a category page with the categories page. I now understand what you were suggesting, and it is a good solution. Thanks!

@yariplus The issue is that I would like to have some things on the homepage (e.g. a create topic button, quick links to forum help articles) on the home page but not on the categories page. That isn't currently possible as far as I can tell, but I'd be open to creative solutions.

Bumping this old topic. I would like to add some widgets to the homepage sidebar.The solution posted above isn't ideal because sidebar widgets will just leave a blank sidebar on every page that isn't the homepage. Is there anything in the works to add widgets to just the homepage? Seems strange that the homepage only supports global widgets. The custom homepage plugin seems to be broken for 1.1.2 as well.

So I found a solution that approximates my desired behavior. In the admin panel, go to Extend > Rewards. Create a new reward with the following rules

If User's: Post Count
Is: > 0
Then: Award Reputation
Amount of reputation: 1

This will add 1 reputation for a user on every post, but each post will still start with 0 votes.

@julian Well, that explains a lot. I knew I was missing something very basic. One bad thing about pasting a command every time you want to run it instead of writing the thing out: the mistake you make once is the mistake you make EVERY TIME

Thanks for the sanity check!

Hahaha. Yes, I might have mentioned it.

@julian said in How long does it take a plugin published to npm to show up in nbbpm?:

Hm, odd.

It did work after I manually told nbbpm to update the plugin, so it shows up now: https://packages.nodebb.org/api/v1/suggest?package[]=nodebb-widget-search-bar&version=1.1.2

@deiden26 PUT, not POST

I actually was using PUT and not post, still had the following result for whatever reason

<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.10.0</center>
</body>
</html>

The original command was

curl -X PUT https://packages.nodebb.org/api/v1/plugins/nodebb-plugin-search-bar

EDIT: Now I see you are referencing my "I'll keep posting" comment. I just had my head in the forum lingo!

This would be useful to prevent new users from abusing signatures. It would also allow forums to incentivize members to work towards being able to have a signature.