Technical Support

@charles well looks like bootstrap is required

crap, i forgot to activate the google+ api 😛

@pichalite @yariplus thank you both!

Yeah, that nice 😉

Yes, it'll be okay in NodeBB 1.0.3.
https://github.com/NodeBB/NodeBB/commit/86106971c4dd41a53167be8bc12869c599835e80

You have to fork this repo to be able to edit its content.

Next you're going to browse to an interesting topic, i.e.
https://github.com/NodeBB/nodebb-english/blob/master/installing/cloud/openshift.rst

Use Edit icon near to History label or edit it following any GitHub contributing guide.

I would suggest not to follow that tutorial. For some reason the tutorial clones NodeBB under /var/www which is not required.

Also you will end up using the master branch of NodeBB which is a development version and is likely to have bugs.

@julian @psychobunny I really feel this plugin is important. It makes total sense for a community admin to support their users in a private place which can be tracked in a scalable way.

It has numerous applications from IT support portal, learning communities , healthcare communities, ombudsman group in enterprises. This can bring you lot of customers who looks for 1 stop shop for all community managment. You can highlight this feature in your site as well.

I follow Discourse and have seen them implementing it very recently among lot of requests (In fact they have done it in a complex way within groups functionality). Nodebb plugin approach of using categories IMHO is the right way.

I understand that you would love to do it as a custom service. I feel you would get more visibility if you do it as a community plugin. Since you have already have it for older versions, I feel it is wise to do it for the new versions as well. I would urge you to reconsider the upgrade path for the support plugin.

@PJH Not that I know of. The only way it wouldn't fire is if ajaxify is turned off, and in that situation the classes would get reset anyway.

@Dielan

add the password with in "mongo": { }

so your config.json would look like this

My login page is (almost) entirely blank on my production server but works ok on dev and staging (heroku). I can see the home page and I can create an account and see the profile page, but I cannot login to an existing account:

0_1458589372352_Screen Shot 2016-03-21 at 12.41.34 PM.png

There are no javascript errors in the browser and no errors in the server side log:

21/3 14:33 [24540] - info: NodeBB v0.9.2 Copyright (C) 2013-2014 NodeBB Inc.
21/3 14:33 [24540] - info: This program comes with ABSOLUTELY NO WARRANTY.
21/3 14:33 [24540] - info: This is free software, and you are welcome to redistribute it under certain conditions.
21/3 14:33 [24540] - info:
21/3 14:33 [24540] - info: Time: Mon Mar 21 2016 14:33:07 GMT-0500 (PET)
21/3 14:33 [24540] - info: Initializing NodeBB v0.9.2
21/3 14:33 [24540] - info: Environment: production
21/3 14:33 [24540] - verbose: * using mongo store at xx.xx.xx.xx:xxxx
21/3 14:33 [24540] - verbose: * using themes stored in: /var/www/blahblahblah/live/node_modules
21/3 14:33 [24540] - info: [database] Checking database indices.
21/3 14:33 [24540] - verbose: Checking dependencies for outdated modules
21/3 14:33 [24540] - verbose: [notifications.init] Registering jobs.
21/3 14:33 [24540] - verbose: [meta/css] Minifying LESS/CSS
21/3 14:33 [24540] - verbose: [sounds] Sounds OK
21/3 14:33 [24540] - verbose: [meta/templates] Compiling templates
21/3 14:33 [24540] - verbose: [meta/templates] Successfully compiled templates.
21/3 14:33 [24540] - verbose: [meta/css] admin.css committed to disk.
21/3 14:33 [24540] - verbose: [meta/css] stylesheet.css committed to disk.
21/3 14:33 [24540] - verbose: [meta/js] Minification complete
21/3 14:33 [24540] - verbose: [hotswap] Router with id plugins replaced successfully
21/3 14:33 [24540] - verbose: [plugins] All plugins reloaded and rerouted
21/3 14:33 [24540] - verbose: [hotswap] Router with id auth replaced successfully
21/3 14:33 [24540] - verbose: [meta/js] Client-side minfile committed to disk.
21/3 14:33 [24540] - info: NodeBB Ready
21/3 14:33 [24540] - info: Enabling 'trust proxy'
21/3 14:33 [24540] - info: NodeBB is now listening on: 0.0.0.0:4567

Found the answer - The script starting NodeBB must be in the nodebb directory otherwise the minifier will fail as above. Changed my Upstart script as follows:

+1 for a direct link.

I guess the most direct at the moment is via github (pricing -> github -> Documentation & Installation Instructions) o_O .

docs.nodebb.org <-- now it's in mine too 😛

@qgp9 I can't say exactly how I installed Mongo. When I google, "ubuntu install mongo", my web browser tells me that this page

https://docs.mongodb.org/v3.0/tutorial/install-mongodb-on-ubuntu/

has been visited and it looks familiar. I think it's what I used to guide me.

And, no, I did not compile. And no, I am not using docker.

A detail, since you seem to be interested, is that the install does not leave my system with a functioning "service mongod restart" command. At present, Upstart runs Mongo. "stop mongod" does not work.

managed to fix it by putting the ip address in the facebook url.. not the same one that is in config.json

I first noticed this when I ran into issues with jquery not executing on the ACP, but now with a separate installation, on a totally different server, I'm seeing it again.

I can see clearly that jQuery or javascript isn't executing, but the browser console remains totally blank.

In the previous case, another user here was able to display the contents from his browser console, but mine stayed blank.

This time around, the lavender theme's masonry script isn't executing, but there's no output from my browser console. Thoughts?

NOTE

I am running this directly from an IP address without a FQDN. Could this be part of the issue?

UPDATE

I started up nodebb in dev mode and watched the terminal, but I'm not getting any errors or warning after the site loads. I'm totally stumped why masonry.js isn't loading. It's not even showing up in the console's resources, but there was no error thrown either in the client or the terminal.

@zero how about your webserver config or are you running NodeBB on Port 80?

@charles no. Unless you try this:
https://addyosmani.com/blog/using-npm-offline/

@SimonQ

try the commands here https://community.nodebb.org/topic/8285/easy-nodebb-upgrade-process