String concatenation is highly optimized in JS engines, so the benefits of template literals for performance are small. Using template literals on the client side also makes you incompatible with older browsers.
Also you didn't really relate your advice to NodeBB.
I have a redactor composer plugin on my forum and it looks great and works perfectly when replying or in chat but when I try to actually make a new thread/post I get the error "Category does not exist".
I'm an absolute normie with coding or any of this stuff and I'm doing my best to troubleshoot setting this thing up. Any help would be greatly appreciated.
This is the plugin
This is the tutorial I used to install nodebb initially
install nodebb ubuntu 18.04 With Cloudflare SSL
Additionally I can't seem to get any other composer to work properly. Even the default composer plugins. Usually they will only work to post text alone but not even the preview function works. I'd love to have a redactor composer but at this point I'd probably take any basic composer if it would work.
Thanks for any help in advance!
@Enrique the main problem you seem to be having is that you are not aware that there is a frontend and a backend to NodeBB. You have to wire up the controls from the ACP and make a call to the backend (via websocket, for example), and then you can call server side libraries.
Thank you for your reply, and sorry for lack of information.
http://184.108.40.206:4567/nodebb/ → success to show nodebb.
http://220.127.116.11/nodebb/ → return 404 on parent site(my case is wordpress on nginx).
http://18.104.22.168:4567/ → return misconfigured csrf error on nodebb.
http://22.214.171.124:4567/nodebb → return /nodebbcategories not found on nodebb.
I reloaded nginx.
I setup and restart nodebb each time.
nginx -t → syntax and test is successful.
now I am trying below
I've been noticing some UI issues every time a user logs in or out.
Basically right after you log in, some of the styles do not get picked up (i.e. logo becomes larger, recent-topic cards stop displaying content). Refreshing the page fixes the issue but this is not ideal.
I solved my own problem... I setup a custom notification to fire on the action:post.save hook and I was using the same default standard format for the notifications nid value. Basically I was firing off a notification with the same nid as the notification that auto generates when you post a new topic.
Long story short: Make sure the nid is unique.
@julian said in What hook can I use to filter the topics that appear when accessing /groups/mygroupname ?:
Thank you for this info. My issue is now solved. I was able to perform my serverside filter logic and now everything is great.
FYI - I'm the same guy (username: jremi) that you helped related to the sharing sessions plugin. I was asking you about if using the cross storage solution would work for cross domain cookies.
Thanks again for your help. I really appreciate your assistance.
@julian that flag mechanism for posts will be very good.
We are having huge problems with Google AdSense as its all User generated content and we would love to be able to either
Hide topics from logged out and normal users
Hide ads on topics
On those topics if other users mark it as NSFW, or 18+ tag or flagged as 18+
This will be a huge help. We need this in core and I m sure many others do need this as well.
Google is getting very strict with its content policies now.
Well Ubuntu Server 16.04 is still supported until 2021. NodeJS 8 is an LTS version that is supported until the end of 2019. They might be a bit older, but are well tested and probably more stable than Ubuntu 18.04 and NodeJS 10. Thus it is perfectly up-to-date. But you can do the exact same steps with never versions of Ubuntu and NodeJS.
I'm new with nodebb, i suppose i did some mistake using ./nodebb upgrade and git pull combined, i've make a fresh install and it work. Anyway i've just switched to release and begin to work with plugin and child theme.