Sander, I did update the router code to reflect new file-name, turns out, it was a routing/reverse proxy issue on nginx. I modified the config on nginx.conf and that did the trick.
-anurag On Fri, Sep 12, 2014 at 11:33 PM, Sander Elias <[email protected]> wrote: > Hi Anurag, > > Did you update your router code to reflect the new file-name? > > Regards > Sander > > -- > 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. > -- Twitter: @anuragphadke (https://twitter.com/#!/anuragphadke) -- 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.
