You're clicking on plugin options. Only plugins with user configurable options will show up there. Also, as already mentioned you have to activate them first then restart NodeBB by clicking on the Inactive plugins section in Install Plugins. Then refresh the page after it finishes restarting to see the plugin options.

@Justin-Kamerman-0 sudo service mongod start

I second vscode.

@baris Wow that was quick. Very clean fix. I love you guys. https://github.com/NodeBB/NodeBB/commit/65a65b19c0fdbad8c828a26cc3369b477d0bedb1
http://i.imgur.com/6XInhUZ.png

@PitaJ

Sorry about that. I was having a hard time figuring out how to get those two but I just scp'd them to my local machine. Here they are. Also, the client in that log snippet is my personal IP address and the server is my website address.

https://gist.github.com/insuusvenerati/ac8ed18f2db48c925612da1447717ba4

https://gist.github.com/insuusvenerati/66b0b60bbc318f7e7a248268a0270301

Ok so now the issue is happening with Plugins. Same 404 error. Any ideas?

Edit: Nginx Errors showing up

2017/04/11 00:36:09 [error] 18084#18084: *1080 connect() failed (111: Connection refused) while connecting to upstream, client: [redacted], server: [redacted], request: "GET /api/admin/advanced/errors?_=1491870531143 HTTP/1.1",$

Well I deleted the new config and reloaded the old one and everything appears to be working. Something done during setup must have gone wrong.

@insuusvenerati

Just as a test I renamed config.json and ran sudo ./nodebb stetup again resulting in a default config. The issue does not occur there at all. Seems like it could be caused by redis somehow.

I've just installed a fresh NodeBB on a DigitalOcean box. My issue is when selecting a theme in Appearance > Themes and restarting NodeBB everything seems to work. However, the theme does not actually load. Homepage remains unchanged but everything seems to work on the frontend. When checking Plugins > [theme] to change options for the theme, however, I get a 404. So far i've gottan 404s on:
/assets/templates/admin/plugins/material.tpl
/admin/plugins/material
/api/admin/plugins/lavender
/assets/templates/admin/plugins/lavender.tpl

No errors occur on NodeBB startup. While in ./nodebb dev an error occurs after trying to load Plugins > [theme]

Error: Failed to lookup view "admin/plugins/lavender" in views directory "/opt/nodebb/build/public/templates"
    at EventEmitter.render (/opt/nodebb/node_modules/express/lib/application.js:580:17)
    at ServerResponse.render (/opt/nodebb/node_modules/express/lib/response.js:966:7)
    at content (/opt/nodebb/src/middleware/render.js:70:15)
    at /opt/nodebb/node_modules/async/lib/async.js:718:13
    at async.forEachOf.async.eachOf (/opt/nodebb/node_modules/async/lib/async.js:233:13)
    at _parallel (/opt/nodebb/node_modules/async/lib/async.js:717:9)
    at Object.async.parallel (/opt/nodebb/node_modules/async/lib/async.js:731:9)
    at async.waterfall.str (/opt/nodebb/src/middleware/render.js:65:12)
    at fn (/opt/nodebb/node_modules/async/lib/async.js:746:34)
    at /opt/nodebb/node_modules/async/lib/async.js:1213:16
    at /opt/nodebb/node_modules/async/lib/async.js:166:37
    at /opt/nodebb/node_modules/async/lib/async.js:706:43
    at /opt/nodebb/node_modules/async/lib/async.js:167:37
    at Immediate.<anonymous> (/opt/nodebb/node_modules/async/lib/async.js:1206:34)
    at runCallback (timers.js:666:20)
    at tryOnImmediate (timers.js:639:5)

My setup is running Mongo and Redis and I followed the instructions from https://nodebb.readthedocs.io/en/latest/scaling/index.html so other than the server name and directories for nodebb in my nodebb.conf everything is copied and pasted.

Same issue occurs when running sudo ./nodebb start and accessing the site with the port# with nginx stopped.

Any tips on locating the source of this issue would be greatly appreciated.

@yariplus

Thank you. I'll try this out.

Edit: Worked perfectly! Thank you again.

So it needs to be in JS not CSS?

Does anyone know how to change the progress bar that shows up above the header when going to different pages? I tried overriding .progress-bar but it had no affect.

Throw it up on github and let's get started! I would happily contribue!