Document data privacy implications when using Views caching

[jensschuppe]

When creating a View with a CiviMRF Views Dataset as a data source, the View should be configured to not be cached at all (i.e. changing the default configuration, which is tag-based).

This should definitely be part of the documentation, as leaving the caching on will cause the view be cached the first time it is built after clearing caches and does not update at all. This is important to know since CiviCRM data being fetched via the API can very likely be personal things (as in a "My data" or "My events" views) and will cause information disclosure to other users.

[kainuk]

Hi @jensschuppe, I moved the milestone to 2.1.0. Erik Brouwer has tested the removal of the view updates, so I am going to create the long awaited 2.0.0 release. I think this issue makes sense, but should be part of a general update of the documentation. (Although often when a 0.0. release is made the 0.1 release follows soon)