Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couldn't find a Layout component #9

Closed
subhog opened this issue Mar 28, 2014 · 9 comments
Closed

Couldn't find a Layout component #9

subhog opened this issue Mar 28, 2014 · 9 comments
Labels

Comments

@subhog
Copy link

subhog commented Mar 28, 2014

I've converted old working app from 0.7.x to 0.8.0, now I'm getting this error all the time:

Error: Couldn't find a Layout component in the rendered component tree

There doesn't seem to be anything in the doc regarding how the layouts should now be done.

@cmather
Copy link
Owner

cmather commented Mar 31, 2014

Hi @subhog, Can you include a reproduction repo I can look at?

@cmather
Copy link
Owner

cmather commented Mar 31, 2014

Are you rendering the layout yourself by chance? Or, do you have a layoutTemplate defined on the router?

@subhog
Copy link
Author

subhog commented Mar 31, 2014

layoutTemplate is defined. I'll try to prepare the repo soon.

@nick-merrill
Copy link

@subhog Are you, by any chance, using ngMeteor?

I noticed that adding ngMeteor to my project creates this error, though I haven't figured out why.

@cmather
Copy link
Owner

cmather commented Apr 7, 2014

@subhog, I'm about to push a new release so if there's a bug I can fix here happy to take a look. But need a reproduction. Did you figure out the issue by chance?

@subhog
Copy link
Author

subhog commented Apr 8, 2014

@NicholasMerrill: No, no ngs here.

@cmather: I didn't figure this out. I'm preparing the reproduction now.

@subhog
Copy link
Author

subhog commented Apr 8, 2014

Here's the project I was working on trimmed down to the minimal version that gives the error:

https://github.com/subhog/bug-2014B-blaze-cabinet

There are two paths defined, / and /just-i18n, first with null layout, later with default one. Both show the error in console.

It's entirely possible that it's not a bug, but rather I'm doing something not how it's supposed to be done – but I haven't found a clue in the docs that there's something I should update (I looked a week ago).

@cmather
Copy link
Owner

cmather commented Apr 8, 2014

Hi @subhog, See my comment in your repo. Hope that helps. We should have some better error messaging there though.

@cmather cmather closed this as completed Apr 8, 2014
@cmather
Copy link
Owner

cmather commented Apr 8, 2014

For reference: cmather/bug-2014B-blaze-cabinet@e01597a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants