Entity: Set form display action causes weird dependency issues

This is happening in \Drupal\eca_content\Plugin\Action\SetFormDisplay::calculateDependencies and it goes through all EntityFormDisplay entities and those that have the name of the configured display mode ("new" in the sample model) will be added to the dependencies.

In the sample model that results in this list:

• core.entity_form_display.node.article.new
• core.entity_form_display.node.page.new

I imagine if you go to /admin/structure/display-modes/form you'll find the form display mode there and you can configure it such that it only applies to articles but not page. After that, if you re-save the ECA model, it will re-calculate the dependencies and all should be fine.

Thanks for the quick response.

Unfortunately, the suggested solution appears to complicate the matters even further. By going to /admin/structure/display-modes/form and unckecking the New form display mode for Basic page actually deleted the ECA model!

It's true, dependency management can sometimes be a pain. Maybe you want to try turning dependency management in ECA off? This can be done in the ECA settings. You would have to resave the ECA model afterwards, though.

All dependency was switched off at the ECA settings page, if that's what you refer to.

Insofar setting a display mode on a content type inadvertently deletes the ECA model itself, I actually find this a pretty serious issue.

This is certainly a problem but not an ECA issue. The config entities just have to declare their dependencies, and that's what ECA does. The problem comes from config management and how it handles those dependencies on certain contexts.