I've created a broader solution with pattern matching:
[nodebb-plugin-email-whitelist] Email domain filter plugin

Hey guys,

it's been a while

I've created a plugin for email domain-name filter specification (whitelists, blacklists, both):

GitLab link | npm link

It's possible to specify just any patterns for domain-name matching, like shown within the examples.

It utilizes a matching module (ns-matcher) written by myself because I haven't found any matching modules for order-relevant tasks.

So if you find any bugs, please report them

Examples

Comments (shown with //) are not allowed within the actual syntax (yet).

Simple whitelist:

email.example.com  // Allow email.example.com
email.*.example.com  // Allow email.XYZ.example.com
**.email.abc.example.com  // Allow email.abc.example.com and all (deep) sub-domains
!email.abc.example.com  // Deny email.abc.example.com (sub-domains are still allowed)

Blacklists using negative patterns:

**  // Allow everything
!**.example.com  // Deny example.com and all (deep) sub-domains
email.example.com  // Allow email.example.com

I hope this will be useful, at least I needed it myself

Btw I know the plugin name might be misleading due to the possibility of blacklists/mixtures as well, but I did publish after a long coding session xD sorry.

Pings due to feature requested: @fasterthan @kalihman

To me /api/users returns "userCount":9474

@julian said in how to use own smiley pack:

You'll probably want to check out how emoji packs are installed... but I do believe emoji-extended supports custom uploaded emoji.

@frissdiegurke ?

It's pretty much what @TaLoche said. emoji-static plugin in addition to emoji-extended. This allows you to specify custom emoji sets that need to be activated within emoji-extended plugin page.

Since @MJ upvoted that post, is the question solved for you?

Probably the files are not lost at all - I don't know whether mongod uses a default configuration file or just default configuration if nothing is specified via --config.
Maybe your system uses systemd which means you're supposed to start mongodb with systemctl start mongodb, replace start with restart, stop or status for respective actions.

And if it's not systemd you're using, it might be any other init system with similar structure, in that case we'd need to know more about the system. uname -a would be a start.

@AOKP said in NodeBB and ads - A never ending story:

NodeBB now stopped supporting any DFP code at all

If you're reaching out for help with this, please share some code for sample integration and a version of NodeBB where it worked and one (probably master as of your telling) where it doesn't. Some facts are needed instead of vague "It worked, now it doesn't".

In my opinion the DFP website is shitty as hell, I got trapped within an endless loop between two pages trying to sign up a test account (with checking pricing first). So I'm not doing any further investigation of their service; If you can provide me with some sample code and an API reference I could run further tests as to why the service does not work anymore or how to integrate correctly.
I suspect, the lack of sample code is the main reason, so few people of the community try to help with this. Please tell if it's not possible to provide sample code.

I can't believe this is the fault or a bug on side of NodeBB since NodeBB does provide a reasonable amount of integration hooks within the frontend. It must be either a problem with DFP not being able to integrate well OOTB for single-page applications in general or a problem with your integration code as of my point of view.
The tutorial seems to be out of date and overall dirty hacking the core. I'm sure, with sample code and API reference provided one can set-up a good tutorial or plugin for this.

@zoharm Dependencies are allowed to change within a certain version range. If a package follows the semver specification (and does not introduce breaking bugs) there should never be problems with this for the version ranges NodeBB uses.
But in this case it seems the socket.io-redis (or maybe even one of its dependencies) has introduced such a bug approximately 5 days ago.

I can confirm that the bug is valid - in my experienced opinion - and on the side of NodeBB (or probably a mistake on side of its dependencies).

Reproduced locally with a fresh setup.

@zoharm You can achieve the same circumvention by just using the redis:host property within the config.json (or the setup procedure) for the redis url like

"host": "redis://:my-password@127.0.0.1:6379"

This does not require any code modifications

To keep the reference to the already filed issue: gh#5069

setpixel created this issue in NodeBB/NodeBB

closed NodeBB cannot connect to redis with password #5069

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

@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

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

You can add this to your custom CSS:

a[component="category/post/guest"] {
  display: none;
}