-
Notifications
You must be signed in to change notification settings - Fork 51
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
Having trouble with ensureSignedIn #2
Comments
I guess there is a infinit redirect loop happening.
|
Oops. I fixed that, but apparently never committed/pushed it. I'm running the development version locally, so it was working fine for me. Sorry about that guys. The ensureSignedIn helper now checks to make sure you're not already on an AccountsTemplates route before redirecting. Now we just need @splendido to push that up to Atmosphere when he has a moment! :) |
this would mean bump all useraccounts packages to 1.12.1 :( |
Might be the cause of this bug reported over in meteor-useraccounts/boilerplates#13 |
The issue mentioned at meteor-useraccounts/boilerplates#13 has been resolved (you can read the details in my comment there). @splendido, as far as I can tell, this should be good to go now. I've tested everything I can think of and it's all working. Default routes, custom routes with custom options, etc. Everything behaves as it should. Sorry for the republish inconvenience. |
Bumping now... |
Thanks for the all the work on this.
I've got everything working great if I don't filter out logged out users. All the sign-in, reset password, etc. templates get created and route correctly. But as soon as I do:
FlowRouter.triggers.enter([AccountsTemplates.ensureSignedIn]);
it all stops working.
All the routes are properly redirected to sign-in, and I can see the redirect being called, but the rendering code here never gets called, nor does the route-specific trigger
Any ideas?
The text was updated successfully, but these errors were encountered: