The Configuration Files module doesn't declare its dependency from the Config Tools module, but it uses its configuration object. This means users could just install the Configuration Files module but not being able to change the configuration values shared between the modules (for example, the settings to enable debugging).

I classified it as bug because it's a "bad" UX experience.

Comments

apaderno created an issue. See original summary.

avpaderno’s picture

Issue summary: View changes
anagomes’s picture

Assigned: Unassigned » anagomes
avpaderno’s picture

Title: The "Configuration Files" module doesn't declare its dependency from the "Config Tools" module but it uses its configuration object » The "Configuration Files" module doesn't declare its dependency from the "Config Tools" module but it uses its configuration object
Status: Active » Needs review
StatusFileSize
new5.9 KB

The Configuration Tools module cannot simply be added as dependency for the Configuration Files module, or users who just installed that module (which was possible, since the Configuration Files module didn't declare its dependency from the Configuration Tools module) would get an error message about an installed module that requires another module.

The Configuration Tools module needs to be installed in a post-update hook, and uninstalling it should not be allowed from an uninstallation validation service.

anagomes’s picture

Assigned: anagomes » Unassigned

  • apaderno committed f208a41 on 8.x-1.x
    Issue #3251190 by apaderno: The "Configuration Files" module doesn't...
avpaderno’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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