- Issue created by @dqd
In the moment Conditional fields concept holds contradicting behavior in code which needs deep refactoring. First of all there are actually 2 interfaces, one under manage display for each supported entity type and one under structure/conditional_fields (look at screenshots). Both UIs (which I would love to see unified, but that's a separate issue) split settings into entity types and then in the different created entity bundles inside these types. This assumes that these settings are entity type and bundle agnostic and furthermore misleads the user to the assumption that each setting is just registered to this bundle (e.g. node type article) But in fact reusing fields can cause that conditional field settings and depending fields go with into other bundles.
Additionally when you disable a field temporary in one of the managed form display views (a type can have different forms) all dependency rules from conditional fields in connection with this field are removed (even from database, tested) so these settings are not recoverable in another form nor by enabling the field again. This should not happen and these settings should exist as long as the field is not deleted in this bundle.
It shows off that the way conditional fields is conceptually connected to its fields and entity bundles needs refactoring.
Active
4.0
Code