Few Plugins Working After Update
-
Did you do something like this?
$ cd /path/to/NodeBB $ npm up -
-
Did that, plugins still don't work but now search is broken too.
-
Here is what Solr gives now...
20 result(s) matching "2015", (0.03 seconds)
">{tags.value}{tags.score} -
@Scuzz said:
Theme could be out of date.
Plugin may not have been upgraded for 0.6.x. Hence why they do not work.I don't think that that is the case as the functionality is working here. This is a LOT of core plugins, nothing weird. If basic functionality is going to break over and over again because of the plugin system, I think we need to do away with it. This constant fear of an update breaking everything is becoming a real problem. If this was fringe functionality, fine. But it is not. It is extremely basic.
-
@scottalanmiller said:
{tags.value}{tags.score}
But it is not. It is extremely basic.You're right, it is. Update templates.js then run ./nodebb dev and it'll tell you what the issue is. When you update, it's important to actually check you've updated everything. Not just pulled the latest code and crossed your fingers.
Especially when going from 0.5.x to 0.6.x, changes to plugin code means that old plugins aren't compatible, the changes were made to make NodeBB better in the long run, unfortunately developers either are no longer wanting to, or haven't yet updated their plugins to work with 0.6.x. That's the unfortunate thing with 3rd party plugin developers. It's all well and good making plugins, but if you don't wish to keep them up to date or working with a current version, there's no obligation to do so. -
@a_5mith said:
@scottalanmiller said:
{tags.value}{tags.score}
But it is not. It is extremely basic.You're right, it is. Update templates.js then run ./nodebb dev and it'll tell you what the issue is. When you update, it's important to actually check you've updated everything. Not just pulled the latest code and crossed your fingers.
Especially when going from 0.5.x to 0.6.x, changes to plugin code means that old plugins aren't compatible, the changes were made to make NodeBB better in the long run, unfortunately developers either are no longer wanting to, or haven't yet updated their plugins to work with 0.6.x. That's the unfortunate thing with 3rd party plugin developers. It's all well and good making plugins, but if you don't wish to keep them up to date or working with a current version, there's no obligation to do so.Which is why pushing functionality to the plugins exclusively just makes the platform unstable. That lack of obligation equates to a lack of obligation for the platform to be functional. Fine, but that's the same as saying it's going not to be production ready, ever, and migrating off ASAP is the best course of action because it there is no plan or intention for stability.
-
Every plugin was checked when the upgrade was done that it reported to be at the latest version. So that process isn't working. Telling us to do that doesn't work. I'm rapidly wondering if NodeBB isn't going to be viable. It makes me sad as we've made so much commitment to it, but it just doesn't appear to work. We've been on it for a year and a lot of things are moving backwards.
-
@scottalanmiller Every system that allows third party plugins has this potential problem. Wordpress spent years getting their plugin system right, if you update Wordpress, it tells you a plugin isn't compatible, this is being worked on with NodeBB, but again, takes time to get right and develop.
The NodeBB guys have to release improvements to plugin systems etc, whether plugin developers are still actively creating plugins for NodeBB or not. Look at the number of Wordpress plugins that don't support 4.0+ of Wordpress. If a plugin for 0.5.x doesn't support 0.6.x and the plugin dev either won't update or accept a PR to update it. There's not a lot we can do about that. NodeBB guys made enough noise about the changes before releasing 0.6.x, plugin developers that are still active and developing have changed plugins to support the new system. I've had no problems updating recently, if anything, it's only gotten easier in recent months. If Server Administration is causing you a headache, NodeBB will host your project for you and deal with everything like that on their end. Leaving you with the time to grow your community. I understand your frustrations when it comes to administering NodeBB updates on your machine, but stable versions of NodeBB do work, the plugins you decide to install on them however, are at your own discretion. Notice how nearly every "update stopped my forum", or "this plugin doesn't work" topic is solved by updating a plugin, or disabling an incompatible plugin. The issue here isn't with core NodeBB.
I don't know what OS you're running, so me telling you to run ./nodebb dev may not be applicable to your OS, but whatever method you use to view the logs and start nodebb in development mode will tell you of any issues (if their are any). The issue regarding tag score and tag value in your case is to do with templates.js needing to be updated.
If you have any other issues with getting NodeBB to start, all we need is the output from either nodebb dev or nodebb log, and any issues can be resolved.
-
@scottalanmiller said:
Every plugin was checked when the upgrade was done that it reported to be at the latest version.
Latest version doesn't necessarily mean that it's compatible with the latest NodeBB.
-
@a_5mith said:
@scottalanmiller Every system that allows third party plugins has this potential problem. Wordpress spent years getting their plugin system right, if you update Wordpress, it tells you a plugin isn't compatible, this is being worked on with NodeBB, but again, takes time to get right and develop.
It's that what should be considered core functionality isn't kept in WordPress Plugins, that's the difference. I run a lot of WordPress and have never been concerned that a plugin wouldn't work. Sometimes they don't and I just remove them, no big loss. With NodeBB, important, basic functionality is kept out of the core because they want everything in plugins. That's fine, but combining that with no accountability and no NodeBB made core plugins being supported officially and you just get excuses rather than a quality product.... and at the end of the day that's what matters.
-
I'll get the /dev output as soon as I can.
-
@Schamper said:
@scottalanmiller said:
Every plugin was checked when the upgrade was done that it reported to be at the latest version.
Latest version doesn't necessarily mean that it's compatible with the latest NodeBB.
Of course. I don't expect it to.
-
@scottalanmiller What you consider core functionality and what I consider core functionality are likely to be wildly different. If enough people ask for something to be in core, then I imagine it will be implemented into core. When 1 or 2 users ask for the ability to upload a photo of their cat and have it voted on in a cute or not style vote. I wouldn't want that functionality slowing my forum down in anyway, so it's a plugin. Using plugins made by the NodeBB developers guarantees they will be updated as required.
Possible feature request, separate 1st party and 3rd party plugins. So users can choose to only install plugins made by NodeBB to ensure stability.
-
@a_5mith said:
Possible feature request, separate 1st party and 3rd party plugins. So users can choose to only install plugins made by NodeBB to ensure stability.
That would be very handy. I was under the impression that most of the plugins having issues were "official" ones, but I guess that they are not.
-
It's plugins by Julian that are mostly not working.
-
And PsychoBunny
-
I had used them with the incorrect assumption that as they were by the core team and were such basic features that you would expect to have listed as platform features (basic media) that they were the official plugins.
Is the sentiment that because things like search is in a plugin that it is not an official feature of the platform, for example?
-
@scottalanmiller said:
I had used them with the incorrect assumption that as they were by the core team and were such basic features that you would expect to have listed as platform features (basic media) that they were the official plugins.
Is the sentiment that because things like search is in a plugin that it is not an official feature of the platform, for example?
No, it's a plugin because it allows you to use other plugins like Solr for your searching, instead of the original dbsearch. Or if someone wanted to use something else as their search, completely free to do so.
