-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toastr doesn't appear #1099
Comments
I've been struggling with this for the past couple weeks as well. Hoping someone has a solution. |
I have the same problem. If I change module 2 times than toasts does not appear. I have my own modules client and admin and if I go from client to admin and back than any toast show. With login and logout it is the same. |
Hello @nnixaa its not fixed. Using 3.2.1 version (so latest release) and still not working. |
I have the same problem. |
I still have the same issue. When I navigate from auth module to main module toastr doesn't appear. (version 4.5.0) |
Temporary Work around: |
Issue type
I'm submitting a ... (check one with "x")
Issue description
Current behavior:
First, you go to the dashboard page that includes some codes to show toastr on AfterViewInit. It will show toastr.
And then you go to login page(because of logout),
when you try to open again the dashboard, it doesn't appear.
The global overlay wrapper that contains nb-toastr-container is not in the login page.
so, whenever you get the dashboard again(right after opening one of auth page) angular will re-render layouts and components you made but toastr seems still holding destroyed nb-toastr-container and it's not re-rendered.
Expected behavior:
Showing toastr
Steps to reproduce:
with ngx-admin
Other information:
npm, node, OS, Browser
Angular, Nebular
feature request
is there any way to place toast component manually?
if a page I made is not in layout(but it imports theme module like auth page), there is no way to use toastr.
sometimes we need full screen page with using toastr this way.
The text was updated successfully, but these errors were encountered: