@piyush try installing with npm after opening a terminal in your nodebb folder.npm install nodebb-plugin-whitelist-email-domains
then go to plugin page and activate it, rebuild and restart.
Shouldn't we make new versions of plugins backwards compatible with at least 0.5.x?
Why are people making separate versions for different NodeBB versions?
NodeBB is still **0.**x, so it's not released yet. This is why I don't keep backward-compatibility.
Because if you use software that isn't released yet you are a guy who doesn't care as much about stability as those who use released software only. Therefor you are one of those who stay on bleeding-edge of software. So there is no reason to keep backward-compatibility for those guys.
And as long NodeBB upgrades don't break the old database-content you can update your NodeBB system without problems. If this wouldn't be the case I'd reconsider my thoughts about backwards-compatibility.
Another point is that 0.6.0 breaks some plugins because of renaming of hooks, which would (didn't test it) cause plugins keeping backward-compatibility by containing the old hooks throwing deprecation-warnings on NodeBB-start
but according to the "Plugin/Theme Dev" Group on this board I'm not a plugin-dev, so you can just ignore this ^^ So you now have to consider me as plugin-dev Thanks @julian
EDIT: but according to the "Plugin/Theme Dev" Group on this board I'm not a plugin-dev, so you can just ignore this ^^
oh god rectified!
@frissdiegurke yeah, but in simple things like a hook-refactor like in the case of the
init hook, why are they still not just being backwards compatible? It seems easier.