TypeError: newToast.scope.init is not a function

[dakolech]

I'm using angular-toastr in my project and i've got this error, when first toastr appears.

TypeError: newToast.scope.init is not a function
  File http://page.com/js/vendor.js line 73525 col 15 in _notify/</</<
  File http://page.com/js/vendor.js line 22503 col 27 in processQueue
  File http://page.com/js/vendor.js line 22519 col 27 in scheduleProcessQueue/<
  File http://page.coml/js/vendor.js line 14151 col 7 in completeOutstandingRequest
  File http://page.com/js/vendor.js line 14539 col 7 in Browser/self.defer/timeoutId<

Unfortunately, this error appear always on server (for first toastr) and only one on my local machine.

This is my config:

angular.extend(toastrConfig, {
  closeButton: false,
  iconClasses: {
    info: 'toast-message',
    warning: 'toast-cart'
  },
  templates: {
    toast: 'templates/common/services/alersts_service/alertsServ.html'
  }
});

I'm inlcuding angular-toastr.tpls.js script in my html files.

[Foxandxss]

Weird, but if you're using a different template, don't use the tpls version, but still it shouldn't fail.

[dakolech]

i tried many capabilities, but none works

[Foxandxss]

I see. I would need a reproduction (plunker for example) to be able to test that myself. Or better you could look into the problem and send a PR :)

[dakolech]

i have something like this: http://plnkr.co/edit/RJaDKSJZk3hSSOrfQ9nv

[Foxandxss]

I need a working reproduction, that plunker outputs a lot of errors.

[dakolech]

there it is, working

[Foxandxss]

I see it. Really weird. Will investigate.

[Foxandxss]

Give me some information please. How are you loading the template in your solution? It is a .html file you fetch, it is on templateCache...

I can't reproduce it on my local playground.

[Foxandxss]

Ok, I see where the problem is, now for a fix.

[Foxandxss]

I created an issue at the angular repo, I am not sure if the problem is mine or not.

[Foxandxss]

So the issue is mine, I will think about a way of fixing it. In the meantime I highly recommend you to cache all your templates before booting the app. It is a common thing to do and will fix this issue for now.

[Foxandxss]

I tried to fix this but there are some limitations in angular. In the time being I highly recommend you (if you still use this library) to put your template in $templateCache if possible.

[dakolech]

I did it. Hope it will be fixed in the future.

[Foxandxss]

I am having some talks with a few folks and they all think the same. The end user has to cache their templates beforehand. I agree with them, it is a sane thing todo.

The problem is that angular itself doesn't have some facilites to allow $animate to wait until the directive is compiled (with its children) and I would need to break half library to hack it.

So I am sorry, not a supported feature. Will add a note in the readme.