CODEWITHSUNDEEP
meteor
Steeve Cannon
Steeve Cannon

Reputation: 3682

In Meteor how can I publish one server side mongo collection under different names?

I have a server side mongo collection called Profiles.

I need to publish and subscribe to the entire collection of Profiles if user: adminId.

That way the administrator can edit, updated, etc... each Profile collection item.

But I want users to be able to see their Profile record.

So I tried this...

CLIENT SIDE

MyProfile = new Meteor.Collection("myprofile");
Meteor.subscribe('profiles');
Meteor.subscribe('myprofile');

COMMON - CLIENT AND SERVER SIDE

Profiles = new Meteor.Collection("profiles");

SERVER SIDE - The publishing and subscribing of profiles works fine.

// this returns all profiles for this User
// if they belong to an ACL Group that has acl_group_fetch rights
Meteor.publish("profiles", function() { 
    var user_groups = Groups.find({users: this.userId()});
    var user_groups_selector = [];
    user_groups.forEach(function (group) {
       user_groups_selector.push(group._id);
    });
    return Profiles.find( {
       acl_group_fetch: {
          $in: user_groups_selector
        } 
    });
});

Here is where the problem seems to begin. The Profiles.find is returning collection items because I can output them to the console server side. But for some reason the publish and subscribe is not working. The client receives nothing.

//  return just the users profile as myprofile
Meteor.publish("myprofile", function() {
  return  Profiles.find({user: this.userId()});
});

Any ideas what I am doing wrong. I want to be able to publish collections of records that User A can insert, fetch, update, delete but User B (C, D and E) can only see their record.

Upvotes: 5

Views: 4240

Answers (3)

badslug
badslug

Reputation: 11

I'm not entirely sure of how you're checking for the error or not, but I think you may be running into a gotcha I ran into. When you publish data with the Profiles collection, even though the pub/sub calls use the 'myprofile' name, the data always is always available in the collection that you're returning a cursor for... in this case, the data you publish in the 'myprofile' publication will show up in the 'profiles' collection on the client. The publish call doesn't create a 'myprofile' collection on the client. So if you're trying to find() on the 'myprofile' collection you won't see any data. (Meteor/MongoDB won't complain that the collection doesn't exist because they always will lazily create it when you reference it.)

Upvotes: 1

evdama
evdama

Reputation: 2216

I think your issue is more on the MongoDB side than with meteor. Given your case I'd do two collections (Group and Profile).

Each document in the Group collection would feature an array containing DBRefs to documents in the Profile collection (actually users so I would think about renaming the Profile collection to User as imo that's more intuitive).

Same for the Profile collection and its documents; each document in the profile collection (representing a user) would have an array field containing DBrefs to groups the user belongs to (documents inside the Group collection).

Upvotes: 1

Tom Coleman
Tom Coleman

Reputation: 3037

I think the problem here is that you only need the one collection: Profiles.

So if you just remove the offending line

MyProfile = new Meteor.Collection("myprofile");

Everything should work fine (you'll have both datasets within the Profiles collection).

Upvotes: 0

Related Questions