Meteor 0.8.2 client collection is empty when a new object is inserted

I am working on a project that uses meteor 0.7.2 and it works fine. After upgrading to meteor 0.8.2 I ran into a problem.

When I insert an object into the collection from the client side immediately, the collection is empty and then reloads the data. This happens several times when I update the collection object.

This happens with only one collection. Another collection is working fine.

I am using an iron router and jQuery Sortable .

Can someone please help me with this? (I feel that there is a conflict between minimongo and the master when inserting or updating. If so, why is this happening)

+8
jquery-ui-sortable meteor minimongo
source share
3 answers

It would be great if you could use code that allows behavior to be reproduced. You can create a new meteor 0.8.2 application that just has this collection and see if you can isolate the error.

btw, what is the name of your collection this problem has?

0
source share

Are you sure it is empty? Is he also empty on mongo? And if this is not the case, try making CollectionName.find ({}) on the client side, for example, in the Chrome console.

Do you have uncertainties and automatic publishing is deleted? If you use client-side insertion, you must remember that server-side Meteor.allow is used for this collection.

0
source share

You can check the signed data by adding a meteor packet below

Meteor add msavin: mongol

After installation, press Control + M to switch it.

Other information at https://github.com/msavin/Mongol

or download this and install it and run with credentials. You can check your local database

0
source share

All Articles