-
Notifications
You must be signed in to change notification settings - Fork 280
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
No plugin found named "ensureSignedIn" on server-side #291
Comments
Hi @thomasspiesser, At the moment it is defined only for the client side, I'll publish a patch for this tomorrow! |
oh alright. thanks for the quick reply. |
for now simply wrap the call inside a if (Meteor.isClient) {
Router.plugin('ensureSignedIn', {
only: [ 'here', 'there' ]
});
} |
Hah, just ran into this issue, too. Thanks for reacting to these issues so quickly @splendido! |
I'm still getting this even when I wrap the call in
this logs:
But the 'ensureSignedIn' plugin is missing. I just ran
Thanks! |
See version thank you all for reporting! |
Hi, I just cloned the boilerplate and I am still getting this issue, but only on MUp? |
Ok, we'll have to dig it more... :( |
Actually I fixed it. I am not sure exactly what it was (I was trying many things) but I think it was wrapping in the Meteor.isClient In the meantime I will keep trying to figure out what is wrong with the version I built up from w/ the boilerplate :/ |
I'm also experiencing this. Same version, v1.8.1 instead of 1.8.0. I've also tried putting it in a Meteor.startup call, which did not help. |
Ok, I've deployed the lates version of the boilerplates on:
and everything seems fine! I'll try do deploy with MUP on a DO droplet and see what happens... If you could make a very simple reproduction (with an empty app and without using useraccounts) with a very simple IR plugin, we might think to open an issue for IR! just confirming this is the same as #294, right? |
I cloned this again and deployed to a brand new DO droplet, no errors and everything seems good. My meteor might have been outdated or something earlier, not sure. |
good news then! |
I got this same error today. I am on the latest Meteor on Windows and all my packages are up to date. It worked when i wrapped it in the Meteor.isClient block |
Started getting the same error after latest meteor update on Windows
Getting this below error:
It was working fine earlier before the update ! |
I too am having this error. Thanks. |
Instead, try doing |
That got my project to build! Thank you, however semantic UI is visually much different and buggy now. |
|
Hare! @KrishnaPG |
After updating my meteor to version 1.2.1, i'm not getting Meteor.user() however Meteor.userId() sill returning user ID. |
Hi,
first of all, thanks for the great package!
I have a small problem. When I tried to migrate to the new plugin version of ensureSignedIn, I got this:
Do I need to load the plugin or am I missing something?
This is the function I used in at_config.js in /lib
The text was updated successfully, but these errors were encountered: