Make sure we unsubscribe from published data when switching between views. Probably this is done automatically? But maybe it is not.
Currently it is done that when switching between views all session values are reset. We should check what happens if then some of session values are set back to the previous value. Maybe we should switch to iron-router. So it is necessary to analyze how things are being reactively changed.
One too many reload.
Refactored routing code so that it does not reset all session values
before every routing. See #4
Checked around and it seems that currently the only place where we subscribe but never unsubscribe is when user clicks on the preview link in search results.
Sometimes it is maybe easier to simply do a method call and get data? If reactivity is not important.
Unsubscribe abstract subscription when search result is destroyed. Fi…