https://brokerbacon.com

Landing page is more of a prototype than a final version -- aka needs a lot of work -- but things are progressing.

I figured out my issue...

MongoDB user I was using had a readWrite role, but I guess it needs the dbAdmin role as well. When I tried creating a new user in the nodebb admin area, then it would make things go wonky without the dbAdmin role and result in invalid csrf tokens.

I'm also getting an invalid csrf error while trying to log in if anyone can help me out...

I'm runnning 0.5.7 and reset theme and plugins, but not luck. I looked at mongodb and the sessions collection grows by about 6-9 documents each page request...weird. This is a development instance, so I'm the only one...

Also, I was logged in on Chrome and noticed I couldn't log in on Firefox...just Chrome for some reason. So, I cleared my cache in Chrome and it started giving me errors

@aixnr I'm currently reading 'A History of the Internet and the Digital Future' by Johnny Ryan

Great read so far...

I was at a mongodb meetup in Dublin the other night and they did a presentation on their mongodb management service (I'm not actually sure that's what it's called). Anyway, it's awesome and worth checking out, so I figured I'd mention it: https://mms.mongodb.com/

If you are on AWS, you will mess yourself when you see how simply you can set up a sharded cluster with replica sets.

@Chris Depending on what you want to do you can use hooks like @a_5mith suggested. The hook you'd want to use is: filter:header.build

What I don't like about the hook though is it just appends the new items to the end of the existing ones...I don't think you can change the order, or remove existing ones. I could be wrong though.

-- or --

The menu.tpl for lavender is actually being pulled in from the vanilla theme:
nodebb-theme-vanilla/templates/partials/menu.tpl

So, just copy the menu.tpl from vanilla to your lavender partials folder and change as needed.

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?

Ok, this may be obvious, but I just don't see it...

Why does the navbar (menu bar) not load on the login page?

It looks like it's set up the same way as the other routes & templates which means header.tpl would load which in turn would also load partials/menu.tpl.

What am I missing here?

EDIT: Maybe it's not so obvious after all...?

@arasbm said:

There have been no active topics in the past day

I don't have an exact answer, but I can steer you in the right direction...

src/emailer.js has this code in it:

			Plugins.fireHook('action:email.send', {
				to: results.email,
				from: meta.config['email:from'] || 'no-reply@localhost.lan',
				subject: translated[2],
				html: translated[0],
				plaintext: translated[1],
				template: template,
				uid: uid
			});

A hacky way might be to wrap that method in an if statement like this:

if (translated[1] !== "There have been no active topics in the past day") {
			Plugins.fireHook('action:email.send', {
				to: results.email,
				from: meta.config['email:from'] || 'no-reply@localhost.lan',
				subject: translated[2],
				html: translated[0],
				plaintext: translated[1],
				template: template,
				uid: uid
			});
}

THIS IS NOT AN EXACT ANSWER. I'm just throwing this out there to steer towards a solution. I have no idea what translated[1] would give you...

Using grep helps with this type of stuff...for example from your nodebb root you can do:

grep -r "There have been no active topics in the past day"

It will search recursively through and spit out the file name and line of text wherever it finds the matched string...I use this a lot for tracing functionality through nodebb core. Really helpful if you are writing plugins and want to trace the hooks to their source...