General Discussion

@aixnr I'm currently reading 'A History of the Internet and the Digital Future' by Johnny Ryan Great read so far...

Yes, nice catch @a_5mith. Incompatible themes requiring outdated versions of the vanilla theme often cause npm to abort. It's not a pretty sight

I just updated the roundup, and the episode 2 is available here on Faith.na. Couple things worth mentioning: Previously I posted the episode 1 on Defiance.NightlyArt.com, but then I moved that article to Faith.NightlyArt.com because Faith is my techblog for all long-form articles. There are 66 links of pure awesomeness, so do check it out! I hope this helps. Have a great weekend!

@julian Is this a thing? This would make certain settings (like Pushbullet) able to be put in the same place as all the rest.

Happy Thanksgiving everybody. Us Canadians up north celebrated a month early so there's nothing left to do but shop the black Friday deals XD

@pitaj router and app are both routers, per se. However, router refers to a separate router instantiated specifically for plugins to use. When NodeBB reloads, the plugin router gets regenerated, while the application router does not. This allows plugins to be both activated and deactivated without a full restart. ... You also cannot overwrite existing application routes in app, though you weren't allowed to do that for awhile now.

Wow, thanks.

Nice to see the W3 community has a sense of humour EXAMPLE 6: Such Deep <form enctype='application/json'> <input name='wow[such][deep][3][much][power][!]' value='Amaze'> </form> // produces { "wow": { "such": { "deep": [ null , null , null , { "much": { "power": { "!": "Amaze" } } } ] } } }

Hm... are you using a special theme?

ObjectRocket is pretty keen as well.

I haven't tested but I'm pretty sure, given the experiences of others here, that the actual cause of my NodeBB breakage was dbsearch 0.0.16, so while it's awkward to be told there are all of these upgrades available, I don't think the problem was nbbpm, just a bad plugin.

We mostly use !!var, but filtering an array so you can get rid of falsy values with arr = arr.filter(Boolean) is neat as well

And yes, cleaning out the stale, stray files from when I originally cloned off of vanilla fixed the csrf issues I was having.

@mootzville Thanks!

Ya, so I was dumb...I have a local dev instance and a staging server. I was playing around with some things and forgot to switch the theme back to vanilla which explains why I was missing the navbar for the login screen...boo me. But yes, thanks for pointing that out. The template engine and middleware are making a lot more sense now after looking through the source for the last 2 days... I'm going to start looking to add/update the documentation here soon...some of the stuff can drive you crazy if you aren't familiar with the version changes. Also, after reading through most of core at this point I have to say it's an impressive piece of kit. Thumbs up to the core devs. @julian @baris @psychobunny EDIT: Also, anyone else who comes across this thread...if you really want to save yourself some time banging your head against the wall -- like I did -- take a few days to really dive into the nodebb source. It has been a good lesson in object-oriented javascript -- so many objects -- done right. I've realized I'm approaching things more from a functional perspective, so this has been an eye opener for me.

What kind of changes?

@julian Awesome, thank you.

We've had people test Chrome, FF and IE... none work at the sites with these two firewall products, sadly. HTTPS might work. That's a pain until free certs are widely available Not practical to have tons of them.

You never stop to amaze me on how fast you respond to issues. Thank you!

May be all it needs is time showing it installed now