Community

@magnusvhendin Settings->Advanced User

Obligatory reading:

Advanced user features

uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean. - Advanced user features · gorhill/uBlock Wiki

favicon

GitHub (github.com)

Although it still does allow some stuff I'd rather not see, on balance I tend to favor "Medium Mode" : https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium-mode

Once you're "in the advanced user" modes, enable various "noop" rules to season to taste. Speaking of which, you probably also should read up "Dynamic Filtering": https://github.com/gorhill/uBlock/wiki/Dynamic-filtering

For those more visual and auditory learners: youtuber link: https://www.youtube.com/watch?v=2lisQQmWQkY

Have fun! o/ 🐕

All of our translation efforts are handled on Transifex (https://www.transifex.com/nodebb/nodebb/), but in general, yes... fixes and incorrect translations would be handled there, and custom changes specific to your community you'd make to those files directly.

@pitaj

Global footer widget appearing before footers of other pages. · Issue #6199 · NodeBB/NodeBB

Since updating to nodebb 1.6.1. We noticed our copyright and disclaimer widgets started appearing above footers of other page templates. e.g topic.tpl Here is an example from source code of http://chatrooms.talkwithstranger.com/topic/657...

favicon

GitHub (github.com)

@yariplus said in How to use "posts api":

{posts.post.user.sso-steam:steamid}

Thank you, yari!

@julian how about running one huge find and replace job? Wait... on second thoughts maybe not ha

Also /src/views/, for ACP templates

Yessir 😉

@henrywright said:

this idea wouldn't work if > 1 line change

I was referring to my idea of making a manual 1-line change to the theme core at the point of each upgrade. That would avoid you having to use Git to merge in new commits each upgrade.

Again, although not a clean way of working, it sounds like it'll be easier than what you're currently doing.

@julian Got ya. Thanks for the heads up

For example, I would like to replace username on topic, like shown on the screenshot:Image 1.png

My case is to provide text-area for the user in ACP, so user for example can "change template" of rendering list item.

For example one possible solution:

Store template markup in settings, and ask user to reload NodeBB. In static:load use file system instruments to rewrite template.

But I'm not happy with such solution 😉

I suppose we could add a widget area for the index page template...

@julian Right, I understand. It just makes it difficult to migrate from a more traditional forum like phpBB (which is the most, or perhaps second-most, used forum software today). I think making it easier to migrate from phpBB's format could only help nodeBB gain more ground 🙂 Here is the github issue I opened a couple weeks ago. It was closed, though I hope we can reopen it. I'm more than willing to contribute. Let me know if there's anything I can do.

Posts from child categories are not shown on the home page. · Issue #2549 · NodeBB/NodeBB

This becomes an issue when the parent category does not contain any posts directly, but has several child categories. Is there a way to adjust this behavior? If anyone could point me in the right direction it would be much appreciated! 😄

favicon

GitHub (github.com)

Ok, this works

<!-- IF categories.children.length --> <!-- BEGIN children --> <!-- IF @first -->(Sub-forums: <!-- ENDIF @first --> <a href="\{relative_path\}/category/{categories.children.slug}" itemprop="url">{categories.children.name}</a> <!-- IF [email protected] --> &middot; <!-- ENDIF [email protected] --> <!-- IF @last -->)<!-- ENDIF @last --> <!-- END children --> <!-- ENDIF categories.children.length -->

Just put it somewhere between <!-- BEGIN categories --> and <!--END categories --> in home.tpl

And take both \ from {relative_path}.. it seems that nodebb parses it... so I had to type...

Ya, so I was dumb...I have a local dev instance and a staging server. I was playing around with some things and forgot to switch the theme back to vanilla which explains why I was missing the navbar for the login screen...boo me.

But yes, thanks for pointing that out. The template engine and middleware are making a lot more sense now after looking through the source for the last 2 days...

I'm going to start looking to add/update the documentation here soon...some of the stuff can drive you crazy if you aren't familiar with the version changes.

Also, after reading through most of core at this point I have to say it's an impressive piece of kit. Thumbs up to the core devs. @julian @baris @psychobunny

EDIT: Also, anyone else who comes across this thread...if you really want to save yourself some time banging your head against the wall -- like I did -- take a few days to really dive into the nodebb source. It has been a good lesson in object-oriented javascript -- so many objects 🙂 -- done right. I've realized I'm approaching things more from a functional perspective, so this has been an eye opener for me.

@bentael yes, I believe that is the case.