Technical Support

@shard

Okay. I looked at this and it appears to be a bit more complicated than dropping in a new js. 🙂

Id like to change way emojis suggestions work too. For example if i want to use ":D" in chat i get offered :dagger" (in my instalation). So if i dont want that :dagger: i have to press space to get rid of that suggestion. If i just press ENTER ":D" gets replaced with :dagger:
Turning off that kid of actions would be nice.

Here you go.
https://github.com/NodeBB/NodeBB/pull/5828
After i slept on it, i changed position of hook so it works for both "delay loading" turned on and off. Original place was working only for delay loading turned on so it needed one more hook inside "unloadImages" function and i prefer solutions with less code.

ya, i tried, but still not change, may be take some time go for changes...

You can just add a custom css in the ACP page.

@pitaj said in Post visibility help..:

Hmmmm...

I wouldn't call this security per-say, but it may be a bug in our handling of user page privileges. Make sure that only that other groups don't have any privileges in that category. If that is already so, then please open an issue on Github.

We have one over-arching group that is kind of like "administrator" but from a forum/moderation point of view. The other individual groups have their own sub-categories. So, for each of the sub categories, the over-arching group is assigned and that one group related to that sub-category is assigned.

I'll throw an issue up. Sound like it might be a bug.

@alex-bro change url in your config.json, remove :4567 from the end of it.

Same situation, follow https://docs.nodebb.org/installing/cloud/heroku/ but not works. Also tried https://github.com/NodeBB/NodeBB/issues/5805 and change Procfile to ./nodebb setup && ./nodebb start but not work either.

Any advice?

I have experience on AWS, I can probably make a tutorial for Google Cloud this weekend.

You can also make css and js adjustments from the appearance tab in the admin panel. These are never overwritten.

You could also just make a new location block that points to to .well-known location on your disk.

I have my main forums (https://gamingexodus.com) under /var/www/nodebb/forums, and then have the https://gamingexodus.com/.well-known/stuff under /var/www/.well-known

I would like users to have different dashboards (content) depending on the "groups" the user has subscribed to. Also how would one go about storing additional user info in Mongo?

@countach that's nothing to be worried about for now. It's something that needs to be taken care of on the theme's end. Post an issue on the theme's repository.

@pitaj

Got it figured out. Basically, you have to form a "redirect chain" kinda. I think I was creating an infinite loop of redirection or excluding a specific case (www. for 443 and for 80 separately) in my above nginx config. I ended up having to redirect 80 http://www.domain.com, 80 http://domain.com AND 443 https://www.domain.com all to 443 https://domain.com and then that third block is where all the master logic for the activity goes, if that makes sense.

In my original post, I was combining too many of these cases into just 2 blocks. In addition, I also added location / {} and wrapped that around my return 301 statements.

This fixed the problem entirely with both the domain and the forum malfunctioning. Last but not least, I wanted to mention that I also added proxy_set_header X-Forwarded-Proto $scheme; to the main logic block near the other proxy_set settings, which fixed a csrf error as well. So we're all good now!

Very exciting stuff. I appreciate the quick replies and help. Happy to use NodeBB for my new site!

@baris Okay: I'll focus on the possibility of multiple nodebb processes.

@PitaJ: Gotcha. I'm glad I put exactly what I typed so that you could point out my error. I revisited the documentation and it looks like I'm not starting the app the way it's currently recommended (via nodebb start), so, without having insight into why running node app.js might be a problem, I'm giving that a shot.

With that, the nodebb related output seems to be the same when grepping either 'node' or 'nodebb'... it shows processes for loader.js and app.js in the nodebb directory.

Anyway--I'll see what happens with today's digest. Regardless, I appreciate everyone's help very much.

@Eric-Ladner No, it doesn't upgrade the plugins... or I should say, it didn't used to.

More recent versions of NodeBB call ./nodebb upgradePlugins as part of the upgrade process, and that will upgrade plugins (to whatever version nbbpm says they should be upgraded to)...

However, those plugins that aren't registered with nbbpm won't be touched by ./nodebb upgradePlugins.

It is a custom install, we are trying to get it updated to the latest in steps to ensure nothing is broken.

nodebb mobules should either start with nodebb-plugin- or nodebb-theme- so in your case your theme name should be nodebb-theme-exo-theme

@pitaj Yes true, I tried installing mongo onto my 17.04. The installation was successful but some packages did not work (were not supported).

I had the same problem when I was playing with NodeBB on a $2.5 vps from Vultr (=512MB ram). htop shows me that build process uses all available ram and cpu. Deploying on a decent machine/vps would solve the problem, aternatively, I called build steps one at a time ( eg ./nodebb build languages , ./nodebb build 'client side styles' etc) . Hope this helps.