Angular UI Router - Views in an Inherited State

The first obvious mistake:

You can't specify controller and template on the state while your using views. They are mutually exclusive...

This is because when there is no "views" but a controller and template on the state, UI-Router automatically creates the "views" property and pulls those properties to an "empty" view...

.state('base', {  abstract: true,  templateUrl: 'views/base.html', //Can't do this  views: { // when this is there.    "search": {      templateUrl: "views/search.html"    }  }})

Instead do:

.state('base', {  abstract: true,    views: {      "": {        templateUrl: 'views/base.html'      },      "search": {        templateUrl: "views/search.html"      }    }  })

Second problem:

How views targeting works with nested views etc. is not very logical, it may work well if you restrict your self to one view in one view all the way down, but ones you start working with multiple named views it all gets confusing... Add unnamed views on top and many people gets lost...

The way views work in UI-Router is the worst part of UI-Router...

Given you example I am not even entirely sure of the way to target the search view from your abstract parent state... Might be:

.state('base', {  abstract: true,    views: {      "": {        templateUrl: 'views/base.html'      },      "search@base": {        templateUrl: "views/search.html"      }    }  })

If it can even be made to work... Alternatively you can move the search view out of base.html, but I guess you added it in there for a reason.

The whole view concept is the biggest reason why I ended up writing https://github.com/dotJEM/angular-routing instead.

The Child state should be home.search instead of header.search. In your case, you may want to write some abstract state to hold the layout,

base.html

<div class="row-fluid">    <div class="header">        <div class="span3" ui-view="logo"></div>        <div  class="span9" ui-view="menu"></div>    </div></div><div class="row-fluid">    <div class="content">        <div class="span2" ui-view="sidebar"></div>        <div  class="span10" ui-view="entry"></div>    </div></div>

in app.js

$stateProvider    .state('base',{        abstract:true,        url:'/',        templateUrl: viewBase+'base.html'    })    .state('base.main',{        url:'',        views:{            "logo":{                templateUrl:viewBase+'main/logo.html'            },            "menu":{                templateUrl:viewBase+'main/menu.html'            },            "sidebar":{                templateUrl:viewBase+'main/sidebar.html'            },            "entry":{                templateUrl: viewBase+'main/entry.html'            }        }})

According to the ui-router documentation, when the application is in a particular state—when a state is "active"—all of its ancestor states are implicitly active as well. So, for example, when the "contacts.list" state is active, the "contacts" state is implicitly active as well, because it's the parent state to "contacts.list". Child states will load their templates into their parent's ui-view. I'd reccomend looking over the section of their documentation entitled Nested States & Views to gain a fuller understanding of how to do this.

In the code you have provided us here, the parent state of the search template is home, while

.state('header.search', {    templateUrl: "views/search.html",    controller: "SearchCtrl"})

implies that the parent state of the search template should be header in order for the view to get loaded correctly. So, I believe the following changes to your app.js will fix your issue.

app.js

$stateProvider  .state('home', {    url: "/",    views: {      '': {        templateUrl: "views/mainContent.html",        controller: "MainCtrl"      },      'header': {        templateUrl: "views/header.html"      },      'footer': {        templateUrl: "views/footer.html"      },    }  })  .state('home.search', {    views: {      'search': {        templateUrl: "views/search.html",        controller: "SearchCtrl"      }  })  .state('anotherPage', {    url: "/anotherPage",    templateUrl: "views/anotherPage.html"  });