Profile ocassionally does not attach to user about wekan HOT 6 CLOSED

I am able to reproduce this problem. It seems that there is an unfortunate interaction between three things:

1. Meteor's built-in logic that subscribes a user to their own Users record, including the full profile field.
2. Wekan's 'board' publication, which relies on some complicated magic from the cottz:publish-relations package to publish partial profiles for all members of a board. Somehow this seems to overwrite the profile data that the client receives from (1).
3. Wekan's usage of SubsManager, which implies that subscriptions to 'board' don't get stopped when the user navigates away.

from wekan.

#20 works around the problem.

from wekan.

#21 works around the problem and seems less likely than #20 to cause other problems.
Of course, it still would be good to understand the root problem here! I suspect there is a bug in the cottz:publish-relations package.

from wekan.

Some errors on current version of pull request #20

from wekan.

I believe the main problem is that this cursor will call subscription.added() with an incomplete version of the user's profile. If that call to added() happens before Meteor's autopublish of user.profile happens, then it is the only piece of the profile that the client will see. #25 fixes this problem by avoiding the current user in this 'boards' publish.

from wekan.

Fixed by #25.

from wekan.