Iron Router notFoundTemplate does not behave properly with Nested Routes

Vote count:

0

I understand that how notFoundTemplate works. However Router.configure({ notFoundTemplate: 'notFound' }) does not seem to work properly when used in conjunction with another nested route.

For example, after specifying the default notFoundTemplate, adding '/user/:_id' route below seems to break the notFoundTemplate. It results in showing this message every time:

"Route dispatch never rendered. Did you forget to call this.next() in an onBeforeAction?"

How can I get notFoundTemplate to work when used with a nested route?

I've also tried creating a custom notFound template INSIDE the nested route (check if template exists and if it doesn't, load notFound view) however that didn't work either.

asked 1 min ago

saeho

3

Iron Router notFoundTemplate does not behave properly with Nested Routes