NodeBB Development

Found a "hidden" file in the nginx/sites-available and nginx/site-enabled folders. Deleted that and now I only have one nginx warning left. When running 'sudo nginx -t' this is the result: nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:80, ignored nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful EDIT: Ok i have now also removed the return 301 (line 4) in the nginx server block, I think it also conflicts with the rewrite in line 5. Restarted server/nginx/nodebb And boom HTTPS works. Next thing though, we still don't get to see a greenlock in firefox or chrome. It says something about the site only being partially secure. Any idea why that happens? Now also fixed, our logo was still referring to a http link, removed the domain and just made it point to src="/assets/uploads/system/site-logo.png" PS. any other tips or adjustments on the config files is also welcome

FWIW, it's a few years later -- I was able to log in via elinks (a lynx variant used by one of our members), and though the interface was a little messy it worked. Search seemed to not work (or I wasn't using it right), but I could browse. Writing a reply to a post seemed impossible though, as I got "403 forbidden." Have not tried with JAWS or the like yet. I'm not sure if this is on the roadmap to change but here is a quick note that these are the results as of June 2018.

Same. How do I do this?

@julian Thanks for the update

@arutemu Link. Nodebb supported Nodejs 8. I install Nodejs 8 for NodeBB and Ghost, this is working and look good!

Good stuff

Hi, I'm new on nodebb and I search how show the description of child category. ex: list itemSteet ** Walking Chat here to how walk Thanks to all.

cool, thx

@pichalite Thank you! This working!

There's no baked in way to get that kind of permissions control. It's either all-or-nothing when it comes to the ACP.

there is 1 benefit too in having the topic ID in the URL. but facebook has them too but urban dictionary URLs are SEO friendly (no IDs in URL) and it has massive traffic.

@showlink1 There is at least one plugin that is an example of how to censor posts: https://github.com/ninenine/nodebb-plugin-beep Regular expressions could be used to find offensive words or phrases, but using them wouldn't necessarily be better than a flat list of words to censor. Using regex in practice for this task would actually probably be worse, because of the overhead of having to know how to construct and modify regexes, which can quickly become nontrivial.

@PitaJ I'm using the slick theme.

That should be available in Settings -> Groups [image: 3f5xBje.png]

https://github.com/eshohet/nodebb-plugin-elasticsearch I'm maintaining & improving the elastic search feature here. It's currently not production ready so I haven't published it. Is anyone interested in collaborating? I don't know their querying language too well, but on my local machine it searches posts a bit better than other search provider plugins. I'm also thinking of a feature to auto tag threads and to show more threads like the one you're currently looking at.

If anyone is curious, I found a workaround using jQuery! It's kind of cheaty because it's using time, but basically I set an interval to run every 100ms a total of 100 times. Each time it checks where my posts are (.awge-windows-container) and looks for a highlight class. If it finds it, it will scroll down and cancel the interval. It's cheaty, but it works without disturbing anything Code below var foundHighlight = false; function setIntervalX(callback, delay, repetitions) { var x = 0; var intervalID = window.setInterval(function() { callback(); if (++x === repetitions || foundHighlight) { window.clearInterval(intervalID); } }, delay); } setIntervalX(function() { $('.awge-windows-container').each(function(ind, obj) { if ($(obj).find(".highlight").length > 0) { $(obj).animate({ scrollTop: $($(obj).find(".highlight")[0]).offset().top }, 2000); foundHighlight = true; } }); }, 100, 100);

@jarko You can add a custom css rule in the ACP. .stats-votes { visibility: hidden; }

Hello all, We've just released version 1.9.1. This is a minor patch that closes these issues. Cheers!

Hi, I need a little guidance here. I run a self-hosted NodeBB forum with the default Persona theme and no skin. I would like to switch to the Flatly skin, because its style closely resembles the main site (which is a wordpress thing). But unfortunately when I switch to Flatly some elements become invisible. For example the header in the chat window looks like this, when no skin is selected: [image: KR7MnOU.jpg] But it looks like this when the Flatly skin is selected: [image: YPGEOM9.jpg] The button glyphs are there, but they are hard to find because their foreground color is the same as the background color. Similarly when I watch the forum on my smartphone I cannot see the (black) Chat glyph on the black header background, so it seems like the chat feature is missing. So, I guess I should override or subclass or modify the Flatly skin somehow, or at least some parts of it. And while I am at it I may also change some colors, slightly. But I have no clue where the resources are that I need to edit. So my question is: where in the nodebb directories are the Flatly skin files, and how should I proceed in a way that my modifications don't get lost after a nodebb upgrade? Thanks, Jurjen