Your <ion-nav-bar> generally should be outside the view. Having the <nav-buttons> inside each view gives you the chance to manage them individually if necessary. Like this : http://codepen.io/calendee/pen/ubzDq
In the template you have to remove the script at the beginning of the file.
<!-- The title of the ion-view will be shown on the navbar -->
<ion-view title="Page 1" hide-back-button="true">
<ion-content class="padding">
<!-- The content of the page -->
<a class="button" ui-sref="page2">Go To Page 2</a>
</ion-content>
</ion-view>
A unified navbar does not work for me in nested views. Looks like the <ion-nav-view> tag kills this functionality some how.
I am trying to define a single container like view, where I want to define the navbar and some other things once. Then there is a ion-nav-view tag, where I want to load the nested views. All nested views should have the same navbar.
This sounds like it’s the same like in the example above, but one state deeper in the hierarchy.
Sorry for reviving this old post, but couldn’t find another related one.