0.0.14 should fix this issue. https://github.com/NodeBB/nodebb-rewards-essentials/commit/b2a6caaba0447fd0344f9cda4995983f1019e2a2

_ _ __ __ _______ _ _ _____ _ _ _____ /\ | \ | | \ \ / / |__ __| | | | | |_ _| | \ | | / ____| / \ | \| | \ \_/ / | | | |__| | | | | \| | | | __ / /\ \ | . ` | \ / | | | __ | | | | . ` | | | |_ | / ____ \ | |\ | | | | | | | | | _| |_ | |\ | | |__| | /_/ \_\ |_| \_| |_| |_| |_| |_| |_____| |_| \_| \_____| _ _ _ _ (_) (_) | | | | _ ___ _ __ ___ ___ ___ _ | |__ | | ___ | | / __| | '_ \ / _ \ / __| / __| | | | '_ \ | | / _ \ | | \__ \ | |_) | | (_) | \__ \ \__ \ | | | |_) | | | | __/ |_| |___/ | .__/ \___/ |___/ |___/ |_| |_.__/ |_| \___| | | |_| Pretty much anything can be done by a plugin. The hardest part is probably getting the UI to control such permissions in an understandable way.

@Joykiller said in Proper way to return res.redirect('')?: @julian said in Proper way to return res.redirect('')?: Callbacks don't work all that nicely with async functions... I think stripe.subscribe is called with await and returns undefined before the isValueID method is called and returns. I added asyncs to test, removed them same issue with headers response from res.redirect. Oh i see what this plugin does, I guess i could write it to the session and then call it from there. Argh im at a loss that didnt work either still same header issue. seems like even the other values prob would do the same as mine I duno if the way it was coded from base was correct. Nevermind I got it working with writing to the session first, had an error on previous attempt. Thanks for the help.

That's awesome @baris I'm assuming backwards compatible with the old method, though that ought to be deprecated?

You can customize translations using nodebb-plugin-customize

@PitaJ said in Private Git for install plugins: @Joykiller there's no easy way to keep the links with npm, but yarn is better at not killing them. Ah ok, well ill put up with it. Till I write some bash that checks to make sure the links there or something and if not replaces it after some trigger. I'll look into it later.

@baris said in Username restrictions (Characters): This is the function limiting usernames https://github.com/NodeBB/NodeBB/blob/master/public/src/utils.js#L394 Would anyone happen to know where this function got moved to in the intervening years? Edit: I think I found it, here: https://github.com/NodeBB/NodeBB/blob/master/public/src/utils.common.js#L330

@Fl4shBack51 No problem

I also run into the problem. Whenever I want to save my customized CSS or Header : NodeBB encountered a problem saving changes By the suggestion above, I modify it to message: err.message, then it becomes: Changes Not Saved: unrecognized input What am I supposed to do? Below is my CSS: body { font-family: "Times New Roman"; } <script> (function(){ var bp = document.createElement('script'); var curProtocol = window.location.protocol.split(':')[0]; if (curProtocol === 'https') { bp.src = 'https://zz.bdstatic.com/linksubmit/push.js'; } else { bp.src = 'http://push.zhanzhang.baidu.com/push.js'; } var s = document.getElementsByTagName("script")[0]; s.parentNode.insertBefore(bp, s); })(); </script> Header: <script type="text/x-mathjax-config"> MathJax.Hub.Config({ extensions: ["tex2jax.js"], tex2jax: { inlineMath: [['$','$'], ['\\(','\\)']] }, TeX: {equationNumbers: { autoNumber: "AMS" } } }); </script> <script type="text/javascript" src="http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"> </script> BUILD log: root@iZ94134cujlZ:/nodebb# ./nodebb stop Stopping NodeBB. Goodbye! root@iZ94134cujlZ:/nodebb# ./nodebb build started 2018-02-26T03:00:31.355Z [21693] - info: [build] Building in parallel mode 2018-02-26T03:00:31.358Z [21693] - info: [build] plugin static dirs build started 2018-02-26T03:00:31.363Z [21693] - info: [build] requirejs modules build started 2018-02-26T03:00:31.365Z [21693] - info: [build] client js bundle build started 2018-02-26T03:00:31.367Z [21693] - info: [build] admin js bundle build started 2018-02-26T03:00:31.367Z [21693] - info: [build] client side styles build started 2018-02-26T03:00:31.368Z [21693] - info: [build] admin control panel styles build started 2018-02-26T03:00:31.370Z [21693] - info: [build] templates build started 2018-02-26T03:00:31.371Z [21693] - info: [build] languages build started 2018-02-26T03:00:31.372Z [21693] - info: [build] sounds build started 2018-02-26T03:00:40.698Z [21693] - info: [build] client js bundle build completed in 9.334sec 2018-02-26T03:00:40.698Z [21693] - info: [build] admin js bundle build completed in 9.331sec 2018-02-26T03:00:40.869Z [21693] - info: [build] sounds build completed in 9.497sec 2018-02-26T03:00:41.498Z [21693] - info: [build] plugin static dirs build completed in 10.14sec Witout `from` option PostCSS could generate wrong source map or do not find Browserslist config. Set it to CSS file path or to `undefined` to prevent this warning 2018-02-26T03:00:54.973Z [21693] - info: [build] client side styles build completed in 23.606sec 2018-02-26T03:00:55.041Z [21693] - info: [build] admin control panel styles build completed in 23.673sec 2018-02-26T03:00:55.075Z [21693] - info: [build] requirejs modules build completed in 23.713sec 2018-02-26T03:01:00.042Z [21693] - info: [build] languages build completed in 28.671sec 2018-02-26T03:01:00.051Z [21693] - info: [build] templates build completed in 28.681sec 2018-02-26T03:01:00.053Z [21693] - info: [build] Asset compilation successful. Completed in 28.695sec. root@iZ94134cujlZ:/nodebb# ./nodebb start Starting NodeBB "./nodebb stop" to stop the NodeBB server "./nodebb log" to view server output "./nodebb help" for more commands

@julian Yeah could of been an older bug, I've not yet updated so will let you know. Thanks for replying so quickly btw.

@pitaj thanks again, heres what i've got so far. [image: 21sUdvl.png] Thinking of doing maybe a floating footer but duno how that would work with continuous loading of the posts/threads. Maybe ill do a small marquee with crypto price ticker under the floating menu bar instead.

@baris said in Found a small bug in Groups: Run this in mongodb to remove them, those groups shouldn't be in that set. db.objects.remove({_key: "groups:visible:memberCount", value: "cid:25:privileges:groups:poll:create"}); db.objects.remove({_key: "groups:visible:memberCount", value: "cid:33:privileges:groups:poll:create"}); Awesome, thx for quick response. I've gone and done this and everything is back to normal. I assume it was because of that poll plugin. @Schamper might wanna look at this.

Ok using 6.11.0 LTS and works again no problems. Thx.

@baris much

@julian said in Anyone here able to help with an NGINX config issue?: @Joykiller We're on a pretty old version of Ghost actually 0.7.1 Yeah thats what I thought.

location ~ ^/assets/(.*) { root /home/**/nodebb/; try_files /build/public/$1 /public/$1 @nodebb; Theres no assets folder in that location. Where the heck is it being routed too? lol Oh wait derp, it replaces assets name. PS: I turned cloudflare caching off its in dev mode so thats not the issue.

@pitaj thx but i figured out why it wasnt working as mentioned above, was a js conflict. Question is does this plugin support the new recaptcha invisible that google just came out with a few months ago?

@julian Fixed ha didnt know about the "edit profile" with the dropdown. thx. Also, plugin seemed to work fine. Haven't ran into any errors yet but might customize later on to allow another specific usergroup to view not just admins.

Thanks, yeah I wrote a game server rcon web socket bot, which stores all the player information, so got the just of using mongo update/inserts/find functionality just never made a plugin for nodebb so was kinda weird on how to start lol.

@Joykiller Not sure if you're around anymore but I thought I'd respond anyway. The problem with maintaining a plugin and theme directory is the maintenance aspect. We simply don't have the time to make sure everything is compatible, especially since every plugin created is a community contribution. So we automate. We rely on plugin developers to report plugin compatibility, and serve only those plugins that are marked compatible. There is one downside, however, and that is plugins will quickly disappear in successive revisions of NodeBB unless the authors keep them up to date. So there's definitely space for crowdsourcing as well. If a plugin is not marked compatible by the developer directly, multiple reports of compatibility by the plugin users should also count, and if enough votes come in, then the plugin should automatically be reintroduced. that part isn't in yet, but it's on the wish list.