Problem/Motivation
When running a migration that references a custom migration process plugin I receive the following error:
The "" plugin does not exist. Valid plugin IDs for Drupal\migrate\Plugin\MigratePluginManager are: block_theme, block_settings, block_visibility, block_region, block_plugin_id, field_formatter_settings_defaults, d6_field_instance_option_translation, d
6_field_option_translation, d6_field_field_settings, d6_field_instance_defaults, field_settings, d6_field_type_defaults, field_instance_widget_settings, field_type, process_field, d7_field_instance_option_translation, d7_field_option_translation, d7_f
ield_instance_settings, field_bundle, d7_field_instance_defaults, d7_field_settings, d7_field_type_defaults, d6_field_file, file_uri, filter_settings, filter_format_permission, filter_id, get_langcode, d6_imagecache_actions, language_domains, language
_negotiation, language_types, content_translation_enabled_setting, field_link, link_uri, log, static_map, skip_on_empty, explode, menu_link_parent, machine_name, substr, format_date, extract, make_unique_entity_field, callback, skip_row_if_not_set, mi
gration_lookup, route, array_build, file_copy, concat, get, sub_process, default_value, null_coalesce, flatten, urlencode, entity_exists, download, file_import, file_remote_url, image_import, dom_str_replace, str_replace, default_entity_value, dom, tr
ansliteration, array_shift, entity_lookup, merge, skip_on_value, multiple_values, single_value, entity_generate, dom_apply_styles, file_blob, dom_migration_lookup, array_pop, node_update_7008, d6_url_alias_language, path_set_translated, timezone, syst
em_update_7000, forum_vocabulary, user_update_8002, user_update_7002, d6_profile_field_option_translation, user_langcode, profile_field_settings, convert_tokensSteps to reproduce
- Create Custom process plugin in module/src/Plugin/migrate/process/PluginName.php
- Add plugin to a migration
temp_code:
plugin: get_langcode
source: language- reinstall module
- run migration
Comments
Comment #2
nicxvan commentedThis was a misconfiguration on my part. I was using the output like this:
Which was loading a null plugin. I spun up xdebug and stepped through until I realized I was passing an empty plugin.
Maybe additional messaging for this error would be helpful.
Comment #3
quietone commented@nicxvan, thank you for sharing your experience; it may help others. And thanks also for closing the issue.