Enabling / installing a module is a serious operation with a permanent effect on a site, which normally only happens when a user / developer is actively requesting it, and even then shows a yes/no decision.

Currently, features happily installes modules on cache clear via
- dependencies_features_rebuild(), called from
- dependencies_features_revert(), called from
- _features_restore() via features_invoke(), called from
- features_rebuild(), called from
- features_flush_caches()

This is not the kind of thing that should happen in a regular cache clear / drush cc all.

What was the idea behind this decision?

Comments

donquixote created an issue.