Since Deputy cannot be told to react to random module installations, there's nothing that can be done to be sure any systems defined by a given hook_deputy_default_systems() invocation are probably turned on or off along with the implementing module's status changes. However, a bit of documentation might guide developers to do something like:

/**
 * Implementation of hook_install().
 */
function example_install() {
  module_load_include('module', 'deputy');
  deputy_activate_default_systems('example');
}

/**
 * Implementation of hook_disable().
 */
function example_disable() {
  module_load_include('module', 'deputy');
  deputy_deactivate_systems('example');
}

/**
 * Implementation of hook_uninstall().
 */
function example_uninstall() {
  module_load_include('module', 'deputy');
  deputy_uninstall_systems('example');
}
CommentFileSizeAuthor
#1 deputy.1396820-1.patch6.6 KBGrayside

Comments

Grayside’s picture

Status: Active » Needs review
StatusFileSize
new6.6 KB

Using hook_enable instead of hook_install. Tossing up as a patch because I havent had time to live test the code.

Grayside’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Add uninstall.