If in hook_migrate_api() you define "disable_hooks" for both a migration as well as its group, the group definition is ignored.

The documentation of hook_migrate_api() reads for the "groups" definition:

"groups": An associative array, keyed by group machine name, defining one or more migration groups. Each value is an associative array - the 'title' key defines a user-visible name for the group; any other values are passed as arguments to all migrations in the group.

I would expect that I can define some general hooks to disable for all migrations in a group and add migration-specific ones to migrations where needed.

CommentFileSizeAuthor
#2 migrate-keep_disabled_hooks_for_group-3114144-2.patch890 bytesRonino
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Ronino created an issue. See original summary.

Ronino’s picture

Ronino CreditAttribution: Ronino as a volunteer commented
Status: Active » Needs review
FileSize
migrate-keep_disabled_hooks_for_group-3114144-2.patch890 bytes

This patch merges "disable_hooks" if they are given for both a migration's group as well as the migration itself. The reason group settings are ignored is the way group arguments are added to migration arguments.