I am having an issue on IE it seems be causing an issue with iron-router except clause. As per https://github.com/iron-meteor/iron-router/issues/1414 the weird things is it seems to work find with IE on my localhost test server, but when online I get the issue. It works fine online with other browsers (Chrome, FF & Safari).
So I am after a complete example to see if I am doing something wrong, pls?
This works on Chrome, FF, Safari and IE (when on localhost), as does the old way (Session variable). But when running on my server (remotely) and access via the reset password link, it seems to reload Meteor differently and iron-router seems to ignore the except statement in the onBeforeAction:
Ie it should be ignoring this as appCreatePassword is on the except list.
Would there be a different way that IE processes this? I am a bit stumped here, maybe I am doing something wrong in my code??? happy to take any ideas?
I thought maybe I was doing the reset password thing incorrectly which was messing up the session stuff?
No these settings are configured on the server.
The client has some default ways of interpreting the standard links to capture the tokens.
If you use the code I posted above, you use use your router to pull the tokens from the URLs.
I find these URLs are less prone to issues… however you need to create a dedicated route where the default way Meteor does it just sets a token variable and you can kind of intercept that on any route.