Technical Support

Well, phooey.

What would be a good way (Mongo statement, I suppose) to add every user to a group?

@pichalite wow, i see it, thanks so much for your reply !!! 👍

Maybe we can remove those checks now, they were added before we had the placeholder element in the template.

@Shaun Yeah, the master branch... might have been fixed already.

@yariplus Nope, I just moved away from DO. And yes, for me also it was probably the 3rd time where I had to install a database package manually as previous attempts to apt-get install had failed or installed an outdated version. I really wish they updated database packages more often on Ubuntu repos, since my problem occurred only due to an outdated redis package on Ubuntu 16.04 (Xenial) repo. 😠

gonna look, thanks again!

@baris Thank you. I'm pretty new to Mongo and after a little tinkering I figured out I had to run the following to get it work correctly:

db.objects.update({_key: {$regex: /^user:\d+$/}}, {$set: {"signature": ""}}, {multi: true});

You've put port 8080 in "url". This should be the actual URL that people visit, and not the port on which the server should listen. You can specify the actual listen-port in config.json as follows:

This will fix the emoji-issue you're talking about 😉 (along with many other problems that may come up because the clients are trying an unresolvable port 8080)

Source:
https://docs.nodebb.org/en/latest/configuring/config.html

To be honest I think that the actual issue here is a plugin or a poor setup overall, if not even a custom javascript interefering with one of NodeBB's internals. As of now I had no longs from 0.7.x and up.

How about adding additional info:

Is it possible to use NodeBB as an OAuth2 provider? I searched for the answer to this, but all I found were lots of topics on connecting to other providers.

Hello!!
I want to authenticate my local mongodb server by using springmongoconfig i.e authenticating spring data of mongodb server.

@danielflippance

Have a look at the following post. I do not know if this is precisely the same as your issue but it seems to be in the same family.

@julian said in 'Category Privileges' does not seem to work:

I can confirm that the "Access Topics" privilege is not functioning correctly, so will need to look into that.

However, with "Create Topics" disabled, the "New Topic" button is not present, and the category itself is not present in the composer dropdown, so that privilege is working as intended.

Link Preview Image If a user does not have the "topics:create" privilege in a category, they are denied read access to topics in that category · Issue #4753 · NodeBB/NodeBB

favicon

GitHub (github.com)

Specifically:
@julian said in 'Category Privileges' does not seem to work:

Fixed in latest master, the labels were swapped, so "Access" was actually controlling "Create", and vice versa.

I had to remove mine for now as it works, but in IE and FF it would cutoff the picture, but worked pretty well in Chrome.

Looking to get some NodeBB consulting at the API level, mostly around reality checks on architecture de

I followed the setting from here and got it fixed https://community.nodebb.org/topic/6525/invited-future-users-can-t-register/5

@UncleSam Yep @pichalite is right.. Its lavender with a few html side widgets.

These are the only css changes I have so far :

Changed font by doing this :

@import url(http://fonts.googleapis.com/css?family=Oswald:300,400);

body {
font-family: "Oswald", sans-serif !important;
}

Changed some colors :

a {
color:#346634;
}

a:hover {
color:#234423;
}

.category-box {
background: #f2f2f2;
}

.panel-default {
border-top-color: #6bb85c;
}

.btn-primary {
color: white;
background-color: #346634;
border-color: #234423;
}

.btn-primary:hover {
color: white;
background-color: #234423;
border-color: #234423;
}

.btn-default {
color: #346634;
background-color: white;
border-color: #234423;
}

.btn-default:hover {
color: #346634;
background-color: white;
border-color: #234423;
}

.open>.dropdown-toggle.btn-default {
color: #346634;
background-color: white;
border-color: #234423;
}

.topic .posts>li .topic-title {
color:#346634;
}

.btn-info {
color: white;
background-color: #6bb85c;
border-color: #234423;
}

.btn-info:hover {
color: white;
background-color: #6bb85c;
border-color: #234423;
}

.open>.dropdown-toggle.btn-info {
color: white;
background-color: #6bb85c;
border-color: #234423;
}

.topic .post-bar {
border-left: 2px solid #6bb85c;
}

.tag-topic-count {
border: solid 1px #6bb85c;
background-color: #6bb85c;
}

Changed upvote/downvote to be weed leafs rather than chevron :

.upvote {
background-image: url("http://420.vawta.com/wp-content/uploads/2016/06/2000px-Cannabis_leaf.svg_.png");
background-size: 20px;
}

.fa-chevron-up {
display:none;
}

.downvote {
background-image: url("http://420.vawta.com/wp-content/uploads/2016/06/red-leaf-md.png");
background-size: 20px;
}

.fa-chevron-down {
display:none;
}

Added Custom Background to display on desktop only:

@media only screen and (min-width: 768px) {
body {
background: url("http://www.all-sweets.com/images/white-gradient-5-1920x1080.jpg");
background-size: cover;
background-attachment: fixed;
}
}

Made is so recent post/comments doesn't display on mobile on home page:

@media only screen and (max-width: 950px) {
.category-item .post-preview:last-child {
border-bottom: none;
display: none;
}
}

(This last change makes it look really clean on mobile so it is not so messy)

Hello, after upgrade from 0.8 to 1.0 i have issue with launching forum in the cloud.
It crash with message:
2016-06-30T08:15:39.868567+00:00 app[web.1]: 30/6 11:15 [3] - error: Error: ENOENT: no such file or directory, scandir '/app/public/uploads/sounds'

For image upload im using: "nodebb-plugin-amazons3": "^0.2.4"

@scottalanmiller said in 503 - temporarily unavailable due to excessive load:

So our daily views (as reported by NodeBB) is 32K - 98K.

It sounds like I should be a little amazed that 512 MB of memory works...

I'll have to scale up my Digital Ocean tonight...

@jeff contact him through GitHub. If you find a bug, report it there.

UPDATE:

The solution I've found for this problem is to run the following command inside the NodeBB installation folder

Doing so automatically merges the fixing commit without any further problems, making the Admin panel usable instantly after a NodeBB restart 🙂