blog does not pull in "not found" template (flow router)

[deborah-ufw]

Blog presents empty content where "not found" content should be.

• using FlowRouter
• in FlowRouter routes, a default "not found" route is specified
• it works in the rest of the app
• blog is using a custom BlogPost.html
• the custom BlogPost.html is located in the same client/templates folder as the error-404.html template
• did not specify anything, but blog did not use the FlowRouter "not found" route
• tried specifying blogNotFoundTemplate: 'error-404', in blog-config.js but it didn't work

Tried changing the template name from "error-404" to "error404", adjusting references and re-testing, but it still did not work.

[foobarbecue]

I've been trying to understand meteor-blog's router recently (in router.coffee). Would be great if there's a dev here who can explain it.

It seems it's not really using flow-router or iron-router for the actual routing. I'm using flow-router, and meteor-blog registers a single route for the url pattern /:any* and then seems to do the actual routing "manually." Unless I'm misunderstanding something, this seems like a very bad way of doing things and it's probably the reason that 404s are mishandled. Can anybody confirm or deny?

[hellogerard]

@foobarbecue This is true. This was the only way to support both routers at the same time.