I'm fighting with a strange behavior of Features which doesn't allow to change configuration installed using Standard Profile.

For example, if you don't need comments and remove the comment field on the article then you wouldn't be able to install any feature which provides node.article.default with some deletions comparing to the original config.

Specifically UnmetDependenciesException exception is thrown from \Drupal\Core\Config\ConfigInstaller::checkConfigurationToInstall because \Drupal\Core\Config\ConfigInstaller::findDefaultConfigWithUnmetDependencies finds differencies between the feature's node.article.default and Profile's node.article.default:

  $config_objects = {array} [1]
    core.entity_form_display.node.article.default = {array} [1]
      0 = "field.field.node.article.comment"

While I see the logic in this, I don't see the reasoning. As such an approach means that the feature will not be installable on anything then Standard Profile. But I don't have any references in my feature to that profile.

Comments

OnkelTem created an issue. See original summary.

OnkelTem’s picture

Issue summary: View changes
nedjo’s picture

Category: Bug report » Support request
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

This sounds like a support request rather than a bug. Either way, it would help to list specific steps to reproduce the issue you're seeing.

nedjo’s picture

This sort of error is usually caused by generating one feature but not generating one or more other features that provide configuration that is required by the generated feature.

For example, assuming you've created a custom Features bundle with the machine name example, this would occur if you generated an example_article feature but not an accompanying example_core feature that provides a field storage required by one of the fields provided in example_article.