I love the darkness, makes me feel like I'm in a browser made for hacking lol. I just like dark colors overall since I can read better. I do enjoy their efforts though since it has those add-ons and all. Especially that eyedrop tpp, really handy when I need to copy certain colors from gradients.

@a_5mith said:

@Ralkage That would probably drive me insane. I think a simple option to turn them on or off would be more sufficient.

I'll try that for my first project then, I'll even see how theyboth work and see what drives me insane first haha.

Wish me luck!

@Lafunamor Manage > Users is in the ACP and has a "Ban User" option under Edit. Though it could be possible to add it to profiles based on usergroup in a sense if you have Moderators on your forum.

I'm so used to Vbulletin that we would add a few lines of code to only allow access for certain groups to use lets say in this case:

<li><a href="#" class="ban-user"><i class="fa fa-fw fa-gavel"></i> Ban User</a></li>

This would only be visible to Moderators and Admins and require password entry before banning said spammer.

This is just me rambling but I do know this can be possible with a few edits or a simple plug-in. Maybe add it under the drop-down list under the profile button?

I miss the layout vbulletin 3 & 4 has I'm studying up on jQuery a little more so I know how to make actual Plugins lol

@a_5mith said:

Did you try it with localhost like the docs say? I'm assuming you don't have to symlink it to sites-enabled like with nginx?

Also, as you're on 2.2.22 of Debian, did you do this? Looks fun...

http://www.amoss.me.uk/2013/06/apache-2-2-websocket-proxying-ubuntu-mod_proxy_wstunnel/

^
This works for Ubuntu 12.04 as well, it took awhile but I got it to work.

<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket
ProxyPassReverse /socket.io/1/websocket ws://127.0.0.1:4567/socket.io/1/websocket

ProxyPass /socket.io/ http://127.0.0.1:4567/socket.io/
ProxyPassReverse /socket.io/ http://127.0.0.1:4567/socket.io/

ProxyPass / http://127.0.0.1:4567/
ProxyPassReverse / http://127.0.0.1:4567/

I keep it at 127.0.0.1 because nodebb is on the same server as everything else on it. Try leaving it at 127.0.0.1 and see where that gets you.

@Ted said:

@Ralkage, I think I abandoned vBulletin around the time v4 was first released.
NodeBB is a unique platform. It can be frustrating at times, but I'll not be using another platform anytime in the foreseeable future.

Ugh, there is just too much php involved with vbulletin and it's boring my members when they can't have a proper mobile skin. I like how NodeBB uses bootstrap and I've been getting tips from people that I should start with jQuery before learning Javascript head on. You never know man maybe I can get some plugins flowing as soon as I finish up programming in college next year or even sooner.

@Ted said:

@Ralkage, there's no need to clarify at all. I've been here for some time and I break things frequently. It's one of the reasons they still keep me around.

There are some big changes and developments coming up for NodeBB. We're at a strange crossroads as we're moving towards a new major version and beginning initial implementation of the plugin compatibility tracker. The good news is, things that we break now, should prevent countless issues for NodeBB users in the future.

One day I will become a wise developer as I swear to it this very moment. :neckbeard:

I'm ready to say goodbye to Vbulletin.

Thanks chums!

Needed to clarify why I'm experiencing these things lol. I'm new to the nodebb game so it's gonna get some getting used to for this to sink in.

Edit: Now after reading the pop-up I feel completely stupid lol.....Well, you learn new things everyday no?

Alright so I've noticed that things go horrible wrong when you upgrade plugins through the plugin manager in the Admin CP or even install them. When you get to the point where you activate them they either crash your forum or they are unresponsive and act sorta rogue. I've ran a few tests and broke my forum over 70 times before testing another install method.

It seems the only way to NOT break your forum in half when upgrading plugins to their current versions is to use npm install nodebb-plugin-example from the console and installing plugins that way.

I feel great not seeing my forum break and seeing Your version of NodeBB (v0.5.4) is only cleared to upgrade to v0.7.4 of this plugin. Please update your NodeBB if you wish to install a newer version of this plugin. pop-up every time I try to update my plugins lol.

Is this something that's being addressed in v0.6.0?

I'm running v0.5.4 by the way.

I think he wants an auto reply plugin from what I gather from OP.

I dig it! I'm gonna check this out as soon as I get home

@Sobo85 said:

Invalid Csrf token

I always seem to get Invalid Csrf token when I log into my account (1st main account/admin account) on a new machine lol it's weird as heck lol.

Raspberry Pi huh? I feel the need to look into this myself.

This is ideal for users who just want to focus on certain categories and get updates via notifications about whats going on in those sections.

Helps clean out the notification clutter.

Use this and follow the instructions:

https://github.com/akhoury/nodebb-plugin-import

You can also install this from inside the Admin CP listed under plugins.

A warning though, always make a test database copy of your forum before you try converting it. 9/10 times horrible things can go wrong.

I've tried a few of the bootstrap skins and some are a little buggy ever since I updated to 0.5.4. Just looks weird as heck lol