Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By alexpott on
Change record status:
Draft (View all draft change records)
Project:
Introduced in branch:
8.2.x
Introduced in version:
8.2.0
Description:
Configuration object are always supposed to be namespaced to an installed module's name. For example, if a module is called my_module
only config called my_module.something.yml
is created when placed in the config/install
. Names like my_module_data.something.yml
are NOT supported.
There are two reasons this is important:
- configuration dependencies have to be determine without a module with installed for configuration synchronisation to work.
- cleaning up on module uninstall depends on the name matching. Modules which have incorrectly named config can not be re-installed
If your module supplied configuration with an incorrect name you will need to write a hook_update_N() to rename the configuration.
Impacts:
Module developers