Vague error message on config import: Config x depends on x that will not exist after import

Solutions

The simple answer for this issue is, with your idea search for the missed configuration.

for example in

Configuration core.entity_form_display.node.tool.default depends on the field.field.node.tool.field_sha256sum configuration that will not exist after import.

search for field.field.node.tool.field_sha256sum on your idea and remove them from the dependencies of other file. Before

dependencies:
  config:
    - field.field.node.tool.body
    - field.field.node.tool.field_file
    - field.field.node.tool.field_tags
    - field.field.node.tool.field_sha256sum
    - node.type.tool

After:

dependencies:
  config:
    - field.field.node.tool.body
    - field.field.node.tool.field_file
    - field.field.node.tool.field_tags

then try to drush cim again.

just bear in mind you should remove all the missed configuration dependencies.

Answering my own question, hoping it may help others. The error message above, in my case, indicates a missing configuration file.

My workflow usually involves switching between branches and re-setting the database to its pristine state. Then I try to import the configuration before finishing a piece of work.

It turns out I did not commit some field.storage.* configuration files before I switched branches and re-set the database. Then the import failed and complained about missing configuration. Re-reading the error messages more carefully allowed me to understand the underlying issue.

I used my IDE (phpstorm) local history feature to search for the missing files and restore them. This fixed the issue.

Similar questions

Error: "module does not exist" after I removed a module from the file system without disabling and uninstalling it
I removed a module from the file system without disabling and uninstalling it. And now I have error: Drupal\Core\Extension\Exception\UnknownExtensionException: The module drupalweather does not exist. in Drupal\Core\Extension\ExtensionList->getPathname() (line 522 of core\lib\Drupal\Core\Extension\ExtensionList.php). How to solve this error? I u...
The new version of my module depends on more modules than the old version ... how to ensure module users install them?
I am updating an existing module I have developed. The new version requires a "helper" module that the old version did not (fwiw, specifically "Nodereference Count"). How do I ensure that when people upgrade from the prior version of my module to the new version, they make sure to install the newly required helper module first? Is there something I...
My Feature depends on a module. Do I have to specify that module's dependency, as well?
My Feature depends on Views. Views has a dependency on Ctools. Do I have to specify Ctools as a dependency in my feature as well.
Ubercart need to pay depends on user role
I am using drupal 6.20 and Ubercart 2.0 Like what I asked in the subject. Is there any chance that I can customize a ordering process with or without payment? For example: There are 2 roles of users ( Role A and Role B) Users of Role A need to pay all my products to complete the transaction. Users of Role B don't need to pay any of my products to c...
How to rediret to specific page depends upon user roles
I have 2 user roles. When a user logs in, I want to redirect the user to a specific page based on their role. I tried the Login_destination module, but it has not worked for me. I have also tried using the trigger action, but it has also not helped me. When I used this trigger action, the ajax module threw an unexpected error message.. SO please he...
custom module js loaded before the module which it depends, Drupal.behaviors
The "Drupal.behaviors" doesn't behave as "document.ready", if I use a document.ready I will have the correct map but if I do a Drupal.behaviors, there will be an error related to the openlayers library function which is not found :( After check, the OpenLayers.js is loaded after my module js. Is it possible to make it load after another one ? I tho...

Also ask

We use cookies to deliver the best possible experience on our website. By continuing to use this site, accepting or closing this box, you consent to our use of cookies. To learn more, visit our privacy policy.