I've launched my forum recently, plenty of work to do, but hopefully a good start: https://wewin.ru/

@youhosi bad advice, as number of applications under different users may/will communicate with database
Yes, you might want to add all of them to the same group and set proper permissions etc... But those who are able to do this - will do, others can use 777 on file in directory unaccessible from outside.

redis.conf

port 0
unixsocket /sockets/redis.sock
unixsocketperm 777

nodebb config.json

"redis": {
  "port": "/sockets/redis.sock",
  "host": "",
  "database": 0
}

I was trying to do this, but failed
Seems like there is no way to make nodebb to listen to mongodb socket...

@youhosi said in [nodebb-theme-oxide] Oxide Style! 3.0.26:

I do not have this problem.

i have compared this part of code... This one from persona recent.tpl

<!-- IF loggedIn -->
<button component="category/post" id="new_topic" class="btn btn-primary">[[category:new_topic_button]]</button>
<!-- ELSE -->
<a component="category/post/guest" href="{config.relative_path}/login" class="btn btn-primary">[[category:guest-login-post]]</a>
<!-- ENDIF loggedIn -->

This one from oxide

<!-- IF canPost -->
<button component="category/post" id="new_topic" class="btn btn-primary">[[category:new_topic_button]]</button>
<!-- ELSE -->
<a component="category/post/guest" href="{config.relative_path}/login" class="btn btn-primary">[[category:guest-login-post]]</a>
<!-- ENDIF canPost -->

Maybe you should use loggedIn condition instead of canPost? Or it might be a bug in 'canPost' variable calculations... I would go with safer one, because you are showing 'guest-login-post' button and it doesn't connected with ability to post messages. So probably you should use "loggedIn" variable in all parts of code like this (recent.tpl and popular.tpl).

@youhosi said in [nodebb-theme-oxide] Oxide Style! 3.0.26:

I do not have this problem.

Unfortunately i do have Version is shown like this in ACP:

nodebb-theme-oxide
Installed 4.0.5 | Latest 4.0.5

I finally managed to install your theme, looks great, but there is a bug...

On "/recent" and "/popular" (maybe some others) templates there is a big "authorise to post reply" button, even though i am already authorized. I tried to relogin, it didn't help.

Yeah, so run 8 workers and they all will serve requests. That's how nodejs works.

in nginx create records like this (i have 2 cores, so i am running 2 workers:

upstream nodebb {
  ip_hash;
  server unix:/sockets/nodebb.sock;
  server unix:/sockets/nodebb.1.sock;
}

and then in "location" just use

proxy_pass http://nodebb;

Innodebb config json you can set several ports/sockets (sockets in my example, as they are way better and safe, then ports, just take care aboout proper access rights)

"port": ["/sockets/nodebb.sock", "/sockets/nodebb.1.sock"],

Voila, your nodebb installation uses all cores.

Yes, it works when using Node 10 LTS.

Indeed, i had this lines regarding benchpress... Unfortunately there is no list of supported Node/OS versions on site I am using Ubuntu 18.04 and node 11.9.0, so my guess it should rather be node 10 LTS, as recommended here

Or, now this plugin has template customizations too, great job! Thank you again! I think this plugin should be bundled into the core...

This is completely different and much more complex request.
To achieve functionality I am askin gfor, they have just add a new settings for 'always be able to edit first post' and when checking, if user is allowed to edit post skip checks of 'time, while allowed to edit' setting.

No need to add wiki functionality, just a small tune for posts editing time settings, which are already in core.

@PitaJ said in nodebb-plugin-customize: Customize NodeBB Translations:

./nodebb build

No, no errors, succesfull build, same problem after restart.

Sometimes topics has short summary and updates in first post, so they need to be edited frequently, while other content on forum should not be edited after certain time.

Please add a setting "Always allow to edit first post in topic", i shouldn't be difficult and will come very handy in certain use cases.

The latest one, it looks like this:

Doesn't work as expected...

Input strings are empty for namespace, for language a bunch of '{}'

This is a very usefull plugin, i really look forward to using it.

Git hash is 53af9ec2e806c25a2933ca8440e3f8d21e74bcd5
I just did a clean setup recently, maybe a week ago.

I have set up a number of categories and disabled some of them, it looks like this in admin panel.

But when creating a new post, user still can choose disabled categories!

Steps to reproduce:

1. Create a category
2. Disable it
3. During creation of new topic, choose a disabled category in the categories list. Your new topic will be rejected, because of insufficient rights.

Expected behavior:
Disabled category should disappear from everywhere, including categories list when creatign topic.

@youhosi said in [nodebb-theme-oxide] Oxide Style! 3.0.26:

npm install nodebb-theme-oxide@latest && ./nodebb upgrade && ./nodebb restart && ./nodebb log

After i do this, everything is OK, no errors.
Then i choose Oxide theme in admin panel and do "rebuild and restart". No matter, how i do this, via admin panel or with shell command "./nodebb upgrade && ./nodebb restart" the same error appears during build, when Oxide theme is selected.

2019-02-13T13:28:14.677Z [/sockets/nodebb.sock/13952] - info: [build]         plugin static dirs  build completed in 0.624sec
2019-02-13T13:28:21.883Z [/sockets/nodebb.sock/13952] - info: [build]         client side styles  build completed in 7.826sec
2019-02-13T13:28:23.332Z [/sockets/nodebb.sock/13952] - error: [build]                  templates  build failed
2019-02-13T13:28:23.333Z [/sockets/nodebb.sock/13952] - error: [build] Encountered error during build step
TypeError: Property consequent of ConditionalExpression expected node to be of a type ["Expression"] but instead got null
    at Object.validate (/home/forum/nodebb/node_modules/babel-types/lib/definitions/index.js:109:13)
    at validate (/home/forum/nodebb/node_modules/babel-types/lib/index.js:505:9)
    at Object.builder (/home/forum/nodebb/node_modules/babel-types/lib/index.js:466:7)
    at Object.OpenIf (/home/forum/nodebb/node_modules/benchpressjs/build/lib/compiler/compiler.js:105:14)
    at compile (/home/forum/nodebb/node_modules/benchpressjs/build/lib/compiler/compiler.js:146:49)
    at Object.OpenIter (/home/forum/nodebb/node_modules/benchpressjs/build/lib/compiler/compiler.js:118:246)
    at compile (/home/forum/nodebb/node_modules/benchpressjs/build/lib/compiler/compiler.js:146:49)
    at compiler (/home/forum/nodebb/node_modules/benchpressjs/build/lib/compiler/compiler.js:160:20)
    at compileFallback (/home/forum/nodebb/node_modules/benchpressjs/build/lib/precompile.js:32:17)
    at Promise.try (/home/forum/nodebb/node_modules/benchpressjs/build/lib/precompile.js:93:88)
2019-02-13T13:28:25.921Z [/sockets/nodebb.sock/13952] - info: [build] admin control panel styles  build completed in 11.863sec

I have node v. 11.9 installed on Ubuntu 18.04, in case that helps.

@youhosi Any idea why i can not install your theme on latest NodeBB installation?

I still didn't get it. Can someone write a short instruction?

So, we have in file /public/language/en-US/pages.json key "unread" with value "Unread Topics"
What should i do, so when user selects en-US language, she will see not "Unread Topics", but "Some other phrase" where 'pages.unread' placeholder is used?

Of course i do not want to change this string value directly in the language file, as it will be overwritten during future updates. But what should i do?