Client filtering doesn't work! ([email protected] + alethes:[email protected])

[thekuzia]

My code:

/lib/conf/pages.js

Pages = new Meteor.Pagination(Posts, {
    availableSettings: {
            filters: true,
            sort: true,
            limit: true,
        },
    itemTemplate: 'post',
    perPage: 10,
    sort: {
        createdAt: -1,
    },
});

/client/app/home.js

Tracker.autorun(function(){
    Pages.set({
        filters: {
            post_type: Session.get('ses_filter_post_type'),
        },
    });
});

Template.home.events({
    'click .js_filter_post_type': function(e){
        e.preventDefault();

        Session.set('ses_filter_post_type', $(e.target).data('value'));
    },
});

What am I doing wrong?
Thanks.

[thekuzia]

Thanks a lot to @fletchtj and this issue #131.
I modified my code a bit, and its works!
With auth function - returns only owners posts, and client filtering is work nice.

My code:

/lib/conf/pages.js

Pages = new Meteor.Pagination(Posts, {
    itemTemplate: 'post',
    perPage: 10,
    sort: {
        createdAt: -1,
    },
    filters: {},
    availableSettings: {
        filters: true,
    },

    auth: function(skip, sub){
        if(!sub.userId){ return false; }
        var owner = Meteor.users.findOne({ _id: sub.userId }),
            userSettings = PostPages.userSettings[sub._session.id] || {},
            uFilters = userSettings.filters || this.filters,
            uFields = userSettings.fields || this.fields,
            uSort = userSettings.sort || this.sort,
            uPerPage = userSettings.perPage || this.perPage,
            _filters = _.extend({owner: sub.userId}, uFilters),
            _options = { fields: uFields, sort: uSort, limit: uPerPage, skip: skip };
        return [ _filters, _options ];
    },

});

[abate]

I've also noticed, that it does not work if you don't specify which fields you want to fetch. You can do it with the auth function, or you can specify fields: { "username": 1, "emais.0.address": 1 } in you inital page definition. Without it, the code is going to generate a query with {fields: {} } resulting in an (almost) empty result.