It's quite hard to parse big blocks of code like that, it would be easier
if it was in a plunker.
A couple of suggestions:
- It looks like you're use Yeoman, check that you don't have a script error
by stopping and restarting the service and looking for errors. Sometimes if
I have a syntax error it will silently stop parsing files, albeit I'm using
CoffeeScript.
- Throw some alerts or console.logs around the router file and make sure
it's actually parsing the router file. Your code problem might not be the
router but something else.
Sam
On Tuesday, 4 February 2014 10:22:01 UTC+11, Marc B wrote:
>
> Ok, if I change this line in index.htm
>
> <div ng-view class="container"></div>
>
> to
>
> <div class="container" ng-controller="contactController"></div>
>
> and I copy the entire contact of views/contact.htm witin the starting and
> ending div, the data gets displayed.
>
> So somehow the router is not kicking in... it's not activated...
>
> When I request the page with 127.0.0.1:9000 the url does not change to "
> 127.0.0.1:9000/#/contacts" even though the router says
> .otherwise({redirectTo:"/contacts"}). This should change the url.
>
> There is no error in FireBug (Firefox) or in Batarang (Chrome). So I don't
> get any feedback on missing includes etc...
> Could it be that the browsr simply cannot parse something and so Angular
> is not able to get to it and is unware of anything going wrong?
> How should I figure out that... Could it be HTML syntax error? Missing
> tag??? No hints from FireBug console window...
>
> Marc
>
>
--
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/groups/opt_out.
