@baris So I have looked at this in greater detail and here are the problems 1 I see. The sortedset really only records two bits of information: the UID and the filename. If anything more is needed the filesystem will have to be queried and logic added to evaluate the file. My view is I'd rather store this in the DB and pick it up in a single query than collect the data from the filesystem on the pageload. This process lacks the post validation check for uploads. This leaves debris in both the database and on the file system. I didn't spot a cleanup system that might take care of this. 1 These are from the perspective of the problem I think I am trying to solve, aside from the couple I saw that are duplicates of issues I created in my own efforts.

I'm working on a plugin that programmatically adds group and/or user perms to a dynamically created category. I mimicked the call used in the write API, but I'm not sure I'm constructing the perms correctly - and that still doesn't answer the issue of single user perms for a category.

Oh, well npm test does exactly what travis does, you don't need to worry about coverage. Just add a test for any function you add.

Finally got a chance to come back to this. Well. That was mind numbingly stupid. So doing a ./nodebb reset -a probably shouldn't also disable the default composer.

I've been trying to get a few tweaks made on the fileownership plugin I started last week along with another of mine that is dependent upon its data and I've run into a wall. As posted last week, it was listening for the fileUpload hook. The problem with that is you end up putting data in the database for a file that might be decoupled from the message ( deleted, etc. ) and then you end up with file references cluttering the database. Today I moved it to the topicPost/topicReply filter. This was a little better in that I knew I was dealing with the final state of the attached files for an initial post/reply ( fails utterly with edits... ) message but the file has not been moved/cloned from "/tmp" to the nodebb filesystem making it difficult to get any metadata ( size, etc ) from the file. I tried moving it to the topicPost/topicReply actions, which occur later - but it was rather inconsistent. This has me thinking a few things. One - I'm doing a lot of this wrong headed and I need to completely rethink storage to account for editing messages. Two - I need a hook that fires after the file has been moved from the tmp filesystem into the nodebb space. Does one exist?

@shard Okay. I looked at this and it appears to be a bit more complicated than dropping in a new js.

@pichalite said in Firing off client side javascript in a partial: @Shard take a look at this plugin as reference https://github.com/pichalite/nodebb-plugin-reactions/blob/master/lib/client.js#L10 That function is setup to run on the topic page. You can do that similarly for profile page. Well, I was part wrong. Seems that runs kinda inconsistently that way. I discovered I couldn't pass the array as above from ( {myplugin.thearray} ) as the argument, found I couldn't iterate through that array unless I converted it to an array of objects. But it won't launch in the iterated loop... Augh.

I'm working on a plugin that filters out a specific file type and relocates them to a different folder. Everything works as I want except for two issues that I expect are approximately the same solution. Since uploadFile fires on all files, I need to do an early filter against the extension/mimetype and exit out on a non-match. When I do so, I am firing the callback with (null, data ) where data is the past object for the filter then returning. The resulting link that shows up in the message has a bad URL. Similarly, when it passes the extension check, it throws an exception due to the uploaded temp file being moved by my plugin. I assume in both cases this is an issue with what need to get sent back when the filter wraps up its business for the rest of the "upload" flow. Looking at uploads.js hasn't helped me parse it out. Looking at the imgur plugin has me more confused than understanding. Anyone know what needs to occur here?

There are a few methodology issue I have here right now. The biggest being that the upload hook fires before a post is posted. This means files that aren't uploaded ( edited out after uploading ) with the post get stored. I need to sort out how to move this to the post hook and process that instead. Learning curve and all. For the moment, this works well enough for the other work I need so I'll be more focused that way for a bit, but I expect to come back to this for enhancement shortly. If you have requests/feature ideas Add it to the issue tracker on bitbucket. https://bitbucket.org/abquintic/nodebb-plugin-fileownership/issues?status=new&status=open

@Bri Beaut. This looks like the exact kind of thing to crib from. Thank you.

Has anyone tackled this for a project? I assume the less files can be shared with some planning. Any tips?

Been away from nodeBB for a bit - the last project I was working with it for went another way. Have something new in the works but I'm still trying to find some integrations. I've been asked to see if anyone's had any success with a cart integration. Something where the forums and the cart SSO and are "thematicly" seemles without having to spend a lot of jiggerypoking keeping themes in sync. I expect this is a no, but. For that matter, anyone just have the SSO part down? Thanks!

@Shard just check NPM. All supported plugins for your NodeBB install can be found in the ACP.

Aside from building some pretty if/else blocks, is there any way to specify a distinct template for a particular forum or subforum?

I have been asked to have the ability to have a few bits of breadcrumbable static content and I'm... not too keen in building a layer on top of node for these few exceptions. Has anyone tried implementing .something like this by either some sort of static content plugin or ( lazier? better? ) single topic sub forums?

This would explain my confusion. Good. Less work for me.

It was an updated pull from a clean install. I don't do any nodebb hacking - just plugins. Let me pull a fresh clean

That's correct, Persona is the new vanilla

@julian Dunno what was wrong that day. Did a pull to update, then did the same steps as I had before and it decided to work. Go fig.

Never finished it. (Did I publish it on npm? Oops?) Since then there has been a few gamification plugins built, for example by @nicolas