- 🇺🇸United States somebodysysop
#6 works for me as well!
#6 worked for me as well. The problem is that it created an entirely new problem by deleting the configuration. Fortunately I was able to copy the configuration from a duplicate site. But, we really need another solution to this problem.
- 🇵🇱Poland adpo
I have the same problem, where I need to delete configuration from my three custom modules.
I would like to know avoid this situation in future. Why does it happen, how to remove the dependency?
What is the reason for this error?
- 🇺🇸United States somebodysysop
This is how I resolved my issue: https://www.drupal.org/project/drupal/issues/3335049#comment-14881197 💬 Configuration core.entity_view_display.paragraph.nested.default depends on the field.field.paragraph.nested.layout_builder__layout configuration that will not exist after import. Fixed
Essentially, a configuration exists in the source site that does not exist in the destination site(s). So, the strategy, other than deleting the configurations in the destination site config table, is to make sure the configuration in question is duplicated in the source site.
I do not know what the issue is with "admin_quotation_settings", but if it's in a module that's enabled in the source but not the destination, you can easily fix the problem by enabling that module in the destination.
If, as in my case, the configurations on both the source and destination sites are exactly the same, then you can try what I did: Go to the settings page for that configuration on the destination site, and simply re-save it. I know, simple. But it worked for me.
- 🇬🇧United Kingdom entropea
Having same issue in 9.5. Modules don't list these dependencies and are in the extensions.yml. Could this be a config split issue?
- 🇹🇭Thailand AlfTheCat
I exported a view as a single item, and after deleting and re-creating a field that is included in the view (same machine name) I try to run the import, all on the same site. Validation fails and it won't let me import, stating: "Configuration update.settings depends on the Update Manager module that will not be installed after import."
I don't understand how Update Manager is a dependency of a view, and there is no reference to it in the view export code either. It wasn't installed when I exported and isn't installed when I attempt to import either. Very strange behavior, I don't have config split installed. Drupal 10.2.3.