That was it exactly! Thanks much Matthias. On Friday, November 7, 2014 2:22:28 AM UTC-8, Matthias Dietrich wrote: > > How did you define your controller? Note that since 1.3.1, global > controller constructors are deprecated and no longer supported: > https://github.com/angular/angular.js/commit/3f2232b5a181512fac23775b1df4a6ebda67d018 > . > > Best, > Matthias > > > On Friday, 7 November 2014 06:16:02 UTC+1, Dane Vinson wrote: >> >> I have this on my main page with the ng-app assigned in the surrounding >> html element. >> >> <div ng-include="'./views/navbar.html'"></div> >> >> <div class="container"> >> <div ng-view></div> >> </div> >> >> navbar.html has a controller assigned in it's top level div >> >> <div ng-controller="NavController"> >> >> All controllers and views in the primary "container" are loaded by >> ng-view and the normal Angular routing mechanism. >> >> Under 1.2.22 everything is fully functional. When I update to 1.3.1 >> everything managed by ng-view is still working as before but the navbar is >> throwing >> >> Error: [ng:areq] Argument 'NavController' is not a function, got undefined >> >> I suspect I wasn't doing something technically correct to begin with and >> 1.3.1 has closed whatever hole I was exploiting but I'm just not sure what >> to start with. >> >> Any thoughts or advice you might have will be appreciated. >> >> Thanks >> >
-- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
