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.
When attempting to sychronise configuration via the UI, missing modules are not correctly identified. Additionally, once the missing modules are identified, the presence of those missing modules does not abort the import of the configurations.
This results in errors from attempting to access modules that do not exist on the site, and no message is displayed to the user to tell them why the sync operation has failed.
Comment | File | Size | Author |
---|---|---|---|
#4 | missing_module-2594479-4.patch | 1.17 KB | gollyg |
#3 | configuration-missing_module_detection-10456809-3-7.x.patch | 799 bytes | gollyg |
Comments
Comment #2
gollyg CreditAttribution: gollyg at Acquia commentedComment #3
gollyg CreditAttribution: gollyg at Acquia commentedIncorrect property name was being passed via the UI, resulting in an empty array for missing modules.
Patch attached.
Comment #4
gollyg CreditAttribution: gollyg at Acquia commentedAdding patch to abort the datastore import process when missing modules are found.
This address the problem that missing modules do not prevent the attempted import of configurations that have those missing dependencies.
The patch returns from the sync process and sets a message showing the modules required for install.
Comment #5
gollyg CreditAttribution: gollyg at Acquia commentedComment #6
Lord Pachelbel CreditAttribution: Lord Pachelbel commentedI tried your patch and it triggered another issue. When I tried syncing changes,
configuration
reported that this module was missing:panels_node_hook
But there is no such module.
The only place I could find that string referenced is in panels_node.module:
So I think that
'base'
key value is being interpreted as a module name.