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.
Problem
A module has a config file with naming bb. another installed module has a config file named aa. The installation don't identify a naming-collision and installs the bb file. That's like aspected, ... but both files could containing the same id bb.
Example
For example you can have a file field.field.node.myfield_bb.yml file in a module but the file contains the id:node.myfield_aa.
This could be in collision with an existing file field.field.node.myfield_aa.yml wich has correctly declared the id:node.myfield_aa.
Proposed solution
- Validate the accordance between file naming and id definition in the file on the module-installation process
- Reject the installation if validation fails
- Show a warning
API changes
Probaply not
Comments
Comment #1
alexpottDuplicate of https://www.drupal.org/node/2140511