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

An outlet was specified but was not found. #10611

Closed
arenoir opened this issue Mar 11, 2015 · 2 comments · Fixed by #10684
Closed

An outlet was specified but was not found. #10611

arenoir opened this issue Mar 11, 2015 · 2 comments · Fixed by #10684

Comments

@arenoir
Copy link

arenoir commented Mar 11, 2015

Upgrading from 1.10 to 1.11-beta-4 I ran into the following issue.

In the router when rendering templates in the renderTemplate hook the into property used to default to the parent template.

The following used to work.

/routes/timecards/day.js
export default Ember.Route.extend(
  renderTemplate: function() { 
    this.render('timecards/day/title', { 
      outlet: 'timecardsTitle',
    });
    this.render('timecards/user/days');
},

It now throws an exception

Error while processing route: timecards.day Assertion Failed: An outlet (timecardsTitle) was specified but was not found.

The error goes away if if add an into property to any render calls with an outlet property.

So it seems the render function doesn't have a default into property when the outlet property is specified.

@ghost
Copy link

ghost commented Mar 12, 2015

Some JSBins illustrating the issue:

1.11.0-beta.1 works: http://emberjs.jsbin.com/viyodiqobi/5/edit
1.11.0-beta.2 onwards doesn't work http://emberjs.jsbin.com/wejekavuba/2/edit

Related to #10478?

@pitou
Copy link

pitou commented Mar 12, 2015

I was able to solve this issue by adding the name of the template where the outlet is located.

App.PostsShowRoute = Ember.Route.extend({
  renderTemplate: function() {
    this.render({
      outlet: "body",
      into: "posts"
    });
  }
});

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

Successfully merging a pull request may close this issue.

2 participants