struggling to wait on subscriptions and multiple subscriptions - meteor

i am really struggling with the iron-router waitOn.
I have a number of subscriptions that i would like to waitOn, it doenst seem to me that iron router is waiting on anything.
I have setup a number of subscriptions (main.js), which i would like to load before the application starts:
Meteor.subscribe("appointments");
Meteor.subscribe("business");
Meteor.subscribe("clients");
Meteor.subscribe("staff");
I have tried almost every configuration i possibly can but i cannot seem to get the "loader" to show itself and wait till all the subscriptions are ready. I have a helper function in the layoutTemplate ('layout') to get a value from the database however findOne() returns undefined/null i assume this is because the router has not waited on the subscriptions...
My router configuration. I would like to understand how i can chain the dependencies or create the dependencies to wait.
Router.configure({
layoutTemplate: 'layout',
loadingTemplate: 'loading',
waitOn: function () {
console.log('Iron router start');
this.subscribe('clients').wait();
this.subscribe('staff').wait();
this.subscribe('appointments').wait();
this.subscribe('business').wait();
this.subscribe('calendar').wait();
},
action: function() {
if (this.ready()) {
this.render('dashboard');
} else {
this.render('loading');
}
}
});

Try changing the waitOn section like this. Also, I think you can remove the subscriptions from the main.js file and write the required/dependent subscriptions in the router's waitOn function for that particular route.
Router.configure({
layoutTemplate: 'layout',
loadingTemplate: 'loading',
waitOn: function () {
console.log('Iron router start');
return [
Meteor.subscribe('clients'),
Meteor.subscribe('staff'),
Meteor.subscribe('appointments'),
Meteor.subscribe('business'),
Meteor.subscribe('calendar')
]
},
action: function() {
if (this.ready()) {
this.render('dashboard');
} else {
this.render('loading');
}
}
});

Try moving your subscriptions from onWait into onBeforeAction:
This may work, but i'm not sure. Usually you define the wait params per route not as a global.
Router.configure({
layoutTemplate: 'layout',
loadingTemplate: 'loading',
onBeforeAction: function () {
console.log('Iron router start');
this.subscribe('clients').wait();
this.subscribe('staff').wait();
this.subscribe('appointments').wait();
this.subscribe('business').wait();
this.subscribe('calendar').wait();
}
});
Router.onBeforeAction('loading');
If this gives you trouble, try using the onBeforeAction above for each of your routes.

Related

Meteor Publications/Subscriptions not working

I'm a bit of a noob and having a bit of trouble getting my publications to work. In my data, I have a number of patients and would like to show the data of a single patient. This is how I have structured my publication:
Meteor.publish('patients.single', function (patientId) {
check(patientId, String);
return Patients.find({_id: patientId});
});
and this is how I have subscribed:
Router.route('/patients/:_id', {
layoutTemplate: 'ApplicationLayout',
yieldRegions: {
'single_patient': {to: 'content'}
},
subscriptions: function () {
return Meteor.subscribe('patients.single', this.params._id);
}
});
I have also tried to subscribe via the actual template to no avail:
Template.patient_details.onCreated(function () {
this.subscribe('patients.single', Session.get("currentPatient"));
});
Publications seem easy in theory, but I just can't seem to get them right. What am I doing wrong here?
It takes time for the subscription to get the data from the server to the mini mongo, so you have to wait for the subscription to be ready, before using the data that It will get for you.
If you are using Iron Router try using waitOn instead of subscribe, that will force the router to wait for the subscription to be ready and will render the loading template while its getting the subscription data.
Router.route('/patients/:_id', {
layoutTemplate: 'ApplicationLayout',
yieldRegions: {
'single_patient': {to: 'content'}
},
waitOn: function () {
return Meteor.subscribe('patients.single', this.params._id);
}
data: function () {
return Patients.findOne({_id: this.params._id});
},
});
You can also use the data property, that way you will have the data available in your template instance.data.
Try this:
Server side Js
Meteor.publish('patients.single', function (patientId) {
check(patientId, String);
return Patients.find({_id: patientId});
});
Router JS File
Router.route('/patients/:_id', {
layoutTemplate: 'ApplicationLayout',
yieldRegions: {
'single_patient': {to: 'content'}
},
waitOn: function () {
return Meteor.subscribe('patients.single', this.params._id);
}
});
In client JS File
Template.patient_details.helpers({
getData : function(){
return Collection.find().getch();
});
Don't forget to call the {{getData}} in the template html file.

Data context is null , template is loaded before collection is ready

Router.route('/form/:_id', function () {
this.render('viewForm', {
data: function () {
return forms.findOne({id: this.params._id});
},
waitOn:function(){
return Meteor.subscribe("forms").ready();
}
});
}
,
{name:"forms.show",
layoutTemplate: 'generalLayout'
});
the data context is empty when i open the link on a new private window .
here's my template manager side
Meteor.subscribe("forms");
Template.viewForm.rendered = function(){
console.log("calling view form");
currentForm = this.data;
console.log("form id",currentForm.id);
}
when i reload the page the dat is retrieved .
here's my loading template with the spin package
<template name="loadingTemplate">
{{>spinner}}
</template>
Router.configure({
loadingTemplate: 'loadingTemplate',
layoutTemplate: 'generalLayout'
});
Change the subscribe method into the route,using waitOn function, like this, just to be sure that template wait until the collection is ready
waitOn:function(){
return Meteor.subscribe("forms");
}
Also don't forget to use a loading template with the waitOn function.
Router.configure({
loadingTemplate: 'loadingTemplate',
layoutTemplate: 'generalLayout',
waitOn:function(){
return Meteor.subscribe("forms");
}
});

SubsManager with Iron-Router new API

any idea how I could connect SubsManager with IR new API?
I use syntax like:
Router.route('/', function () {
this.subscribe('some_subscription').wait();
if (this.ready()) {
//something
} else {
//something
}
},{
name:'1234'
});
Tried subs.subscribe('some_subscription').wait(); but it threw error
Template never rendered, did you forget to call 'this.next()?(of course I initialized object subs)
From the subscription manager docs https://github.com/meteorhacks/subs-manager/#limitations
At the moment, the following functionality doesn't work (patches welcome):
.........................
...............
chained .wait() call in Iron Router (issue - you can use waitOn instead)
so subs.subscribe('some_subscription').wait(); this will throw error
From Iron-router docs https://github.com/EventedMind/iron-router#migrating-from-094
onRun and onBeforeAction hooks now require you to call this.next(), and no longer take a pause() argument. So the default behaviour is reversed. For example, if you had:
Router.onBeforeAction(function(pause) {
if (! Meteor.userId()) {
this.render('login');
pause();
}
});
You'll need to update it to
Router.onBeforeAction(function() {
if (! Meteor.userId()) {
this.render('login');
} else {
this.next();
}
});
Make sure that this.next() is called on onRun and onBeforeAction blocks
and also organize your router code like in lib/routes.js file
//configuration
Router.configure({
layoutTemplate: 'layout',
loadingTemplate: 'loading',
notFoundTemplate: 'error'
});
//keep all your routers under a common function
Router.map(function() {
this.route("index",{
path:"/",
onBeforeAction:function(){ //do something },
data:return something,
onAfterAction
});
});
Finally my answer to the question any idea how I could connect SubsManager with IR new API?
Router.map(function() {
this.route("index",{
path:"/",
waitOn: function() {
return subs.subscribe('some_subscription');
},
data:function(){
if (this.ready()) {
//do something like this.render("loading")
} else {
//do something this.render("mytemplate")
}
},
onAfterAction
});
});

Accessing an argument in a route controller after changing routes programmatically

The iron-router documentation describes changing routes programmatically. The example shows how to pass an argument but I am having trouble accessing this argument in a route controller extension.
In the code below, how would I access the 'baz' value in my waitOn function?
routes.js
Router.configure({
loadingTemplate: 'Loading',
notFoundTemplate: 'NotFound',
templateNameConverter: 'upperCamelCase',
routeControllerNameConverter: 'upperCamelCase',
onBeforeAction: 'loading'
});
Router.map(function () {
this.route('foo', {
path: '/',
action: function() {
Router.go('bar',{_id: 'baz'});
}
});
this.route('bar');
});
bar.js
BarController = RouteController.extend({
waitOn: function() {
// this.params._id does not work
// this._id does not work
// do work and return something;
},
data: function() {
// fetch and return something;
},
action: function() {
this.render();
}
});
Clarification: I would like to achieve this without including the parameter in a dynamic path segment. I just want to pass an argument like any other JavaScript function.
You need to have the param in your path variable
E.g for your foo path if you used
path: '/:_id'
instead of
path : '/'
The addition of :_id is a placeholder for something such as baz to be available with the this.params object.
Then the value would be available with this.params._id, your URL would also change to /baz.

Data not accessible in helper block in Meteor

I have autopublish on.
Template.play.helpers ({
title: function () {
wcount = Workouts.find().count();
console.log(wcount);
}
});
This gives me 0.
But if I'm in the developer console of my browser.
Workouts.find().count()
24
I have recently upgraded to 0.8
If I add waitOn to the Router then I get this behavior every other time I load the page.
Router.map(function() {
this.route('splash', {path: '/'});
this.route('play', {
path: '/play',
template: 'play',
waitOn: function() {
return Meteor.subscribe('Workouts')
}
});
After some help from #Christian Fritz it seems that my problem is that its not waiting on my subscription and if the helper doesn't return anything because its undefined then it doesn't get rerun when the data does get loaded.
I have now turned off autopublish. My server/publications.js is:
Meteor.publish('workouts', function() {
return Workouts.find();
});
My router is:
Router.configure({
layoutTemplate: 'layout',
loadingTemplate: 'loading'
});
Router.map(function() {
this.route('splash', {path: '/'});
this.route('play', {
path: '/play',
template: 'play',
waitOn: function() {
return Meteor.subscribe('workouts')
}
});
});
in play.js
var workoutsSubcription = Meteor.subscribe('workouts');
console.log("workoutsSubscription.ready() is ",workoutsSubcription.ready());
returns:
workoutsSubscription.ready() is false
once or twice then finally reruns when its fully loaded as true. But shouldn't the waitOn mean that it doesn't run that page until the data is there?
You probably want something like this:
var workoutsSubcription = Meteor.subscribe('workout_count');
Template.play.helpers ({
title: function () {
if(workoutsSubcription.ready()){
wcount = Workouts.find().count();
}
}
});
You would need to publish your subscription on the server as well
Meteor.publish("workout_count", function () {
return Workouts.find();
});

Resources