Found the solution, It turns out that I had missed this blog post before upgrading to 1.4.x: https://blog.nodebb.org/introducing-the-build-system-in-v1-4-3/ ./nodebb build

Never mind, it was a simple memory issue that was causing npm install to die. Fixed with these instructions: https://www.digitalocean.com/community/tutorials/additional-recommended-steps-for-new-ubuntu-14-04-servers#create-a-swap-file

I wanted to debug some code I had written in my plugin and did a quick search to see if I could create a Node.js REPL that would function in the context of my plugin. It turned out to be quite simple to do. Just add this to your plugin's static:app.load method: setTimeout(function() { console.log("About to start REPL"); var repl = require("repl"); var util = require('util'); var replServer = repl.start({ prompt: "swf-cms> ", breakEvalOnSigint: true, ignoreUndefined: true, useGlobal: true, useColors: true }); var context = replServer.context; context.require = require; context.module = module; context.context = util.inspect(replServer.context, {depth: 0}); }, 3000); You'll want to wrap this in something to prevent it from running outside of dev mode. Also, load up the context object with anything that you want to be conveniently available in the REPL. FYI, I used the setTimeout to give Nodebb a chance to finish loading before it gives you the prompt. Have fun.

@julian Yikes!

Open an issue on our github so we don't forget about it and link back to this topic I guess.

@julian Agreed. But the goal is good and worthwhile, right?

Glad I could help!

any chance to share the repository? thanks in advance

@pichalite Very cool! Thanks!

@yariplus Thanks! That's very helpful.

Well that works! Thanks!

Is there any built in extensibility to the NodeBB composer that would allow you to submit additional data along with a submitted topic or post? So for example, say you want the users to submit some data to describe their post in a way that is useful for your system, is there a built in extension point that would allow you to add a field (text, select, whatever) to the composer and have that data stored alongside the post? I was able to achieve something like this by hacking the extended data by using tags that are automatically created when the user fills in my custom fields. It works for this scenario, but it would be great if there was a better way to do this. In addition to being able to add custom data to posts, it would be great if you could specify that the custom extended fields only apply to some categories in your system.

See https://github.com/NodeBB/NodeBB/issues/4033

Ooh, @yariplus @frissdiegurke I hadn't really thought of that, but yes, that'd work really well to enhance/load behaviour only if a peer is loaded... ... and only because peer dependencies are such crap on npm..

Same error with persona theme and nodebb 0.9.3. [edit] the error https://le.club.systemes.sonores.rocks/api/topic/thumb/upload 500 Internal Server Error w and h must be numbers

@psychobunny It has options to show/hide the title and render the title as a link to the post itself. So, yeah you can let people go comment on it, or really just make it look like a static piece of content on the site. [image: dYuxEAA.png]

@julian Thanks this did the trick! I used it like this in my client side code: <input id="csrfToken" type="hidden" name="_csrf" value="" /> ... $(window).on('action:ajaxify.end', function(data) { require(['csrf'], function(csrf) { var csrfToken = csrf.get(); console.log('obtained csrfToken: ' + csrfToken); $('#csrfToken').val(csrfToken); }); }); @yariplus I'm not really sure about your specific question. I have a feeling that the csrf tokens are generated based on a csrfSecret that is stored in the user's session. You could check that the session has this loaded on the server side with this: var util = require('util'); console.log('user session' + util.inspect(req)); For me, this results in: user session: { cookie: { path: '/', _expires: Sun Nov 22 2015 09:52:23 GMT-0800 (PST), originalMaxAge: 1209599988, httpOnly: true }, csrfSecret: '70lFS_InV_56D1gvV9TDKgJX', flash: {}, passport: { user: 1 } }

Sweet!

@wktang Yes, this does apply to IS as well.

@lulzdev Sorry for the late reply, but I just ran into a javascript/css inclusion case where I wanted both included as static files for dev. I think just overriding the header.tpl and then linking to static js/css files in your plugin can be good for dev purposes.