Just wondering if I am missing something here, but it seems like iron router doesn’t always wait on one of my subscriptions.
This is my main router code.
The reason why I have the waitOn in the main configure object is because I need the collections available for each and every route. For some reason the second collection isn’t always ready at the time the template loads.
Make sure you subscribe to the right collection and that there is an actual publish for it. I once had a typo in my code and saw weird results because waitOn did not return.
Ok I think I have worked out what the issue is… lets see if there is a way around this.
I believe the issue is that for a brief moment the user is not logged in.
During that time, the publication, assuming the user is not logged in, returns that it is ready.
I don’t share anything in that publication to users who aren’t logged in.
I tried updating the waitOn, but this isn’t working… What should I return to indicate that the subscription isn’t ready.