I have a really old meteor app (updated now) that I am trying to debug. There is a method call inside a template that after the call forces a page reload.
Changing the publish function to a .find({},{}) with no extra fuzz did not change anything, suspecting that the queries triggered an update.
Realizing that the page is refreshed if I change in the mongodb sites collection.
So, re-iterating on the question, how can I avoid a page-reload on the change of the site collection, and just have an update of the few page-details, as with other collections I use on the same page.
I think you are spot on. I have a long list of entities (represented by one component) these are collapsed or expanded and that is stored in a component state, default value is collapsed and set in the component constructor.
The problem appears when the collection is updated, as all component-constructors are called and all components are then collapsed, despite that fact that some of them was expanded by the user.
Any tricks to avoid this constructor call @rjdavid ?
Hmm, I want to know more about that topic of when components are actually mounted or un-mounted by the parent, can you advice me to good docs, I cannot find anything.