I have a similar structure :

Field 1
Field 2
Field 3
Fieldset 4
Field 4-1
Field 4-2
Fieldset 5
Field 5-1
Field 5-2

I would like to have to have the appearance of fieldset 5 to be controlled by Field 4-1 for example and not only by Field 1-2-3.
Also Field 1-2-3 can't control Field 5-x.

The proposed controllers can control only fields at the same level as them in the three level. Why not to propose any field to control any field ?

Comments

jmary’s picture

jmary commented
Category: feature » bug

A I have seen in the code the design of the functionality is made like this at purpose to prevent infinite loop. I'd like to know if the module maintainer will accept to consider a test against infinite loop in place of avoiding infinite loop by feature limitation ?

At this stage I've changed the status from feature request to bug, as IMHO this is a bug in the features design. We should be able to have a field being triggered by any field of lighter weight or contained in a field of lighter weight. Preventing the infinite loop in this case leads to prevent a field of higher weight to trigger a field of lighter weight.

Shouldn't this do the job ?

peterpoe’s picture

peterpoe commented
Status: Active » Fixed

This is possible with current dev. The only thing that you can't to is to control, say, Fieldset 5, from a field within Fieldset 4, if Fieldset 4 is already controlled by some other field.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.