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.
There's a lot of breaking changes being introduced in v0.60. Meaning plugins operate completely differently. The issue you are running into is when you install a version of a plugin designed for 0.60 and attempt to use it on a board running 0.5.4. If you're running 0.5.4, you do NOT need the latest version of every plugin.
The first post in this thread explains the situation pretty clearly.
@Ralkage Caused by 0.6.0. This topic explains the changes from 5.x to 6.x.
The nbbpm compatability was backported. But not sure if an issue exists that causes the update in ACP to update to whatever the latest version is or not.
EDIT: Bloody ninja'd by @Ted.
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?
@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.
@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.
@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.
@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. 
@a_5mith @Ted Now now play nice, upvotes for the both of you.
@Ralkage There's no substitute for the fundamentals. Understanding javascript syntax first will help you in the long run. When I was hiring (way back when in my non-startup days), I'd see lots of devs with "jQuery experience", who couldn't code their way out of a box in plain javascript.
@psychobunny and @baris would make fun of me here, because back then I suffered from the same lock-in, except it was MooTools that I was using instead of jQuery XD
