D7.22
I'm using conditional fields in several configuration without problems.
However in one configuration I cannot get the service to work correctly.
I'm filtering the display of field A using field B as a switch.
If I use any of the "Set of values" choices from field B (eg "any of these values (OR)...") and then enter choices into the "set of values " box, the consequent action does not work; that is filter the display field A. In this case field A is always displayed, and all subsequent conditional_fields functionality seems to be deactivated. If I choose "insert value from widget" it works correctly.
Furthermore if I use the AND, OR, XOR functions then the consequent actions also don't work correctly.
Ive tried all combinations, single list item, keys and values.
I've had a look a the conditional_fields table and it looks OK.
I think this problem to do with the combination of modules I have, I'm using devel and features in this but no other configurations.
This is very strange.
Has anybody ever seen anything like this?

Comments

Tokoh’s picture

Tokoh CreditAttribution: Tokoh commented

Can someone help me with this please?
I have two configurations A and B with conditional fields.
I have the same added two field to each configuration.
Dependee is a list with three values: -none-, one, two three
Dependent is a text field
Conditional fields is set up so that Dependent is only visible if Dependee is one or two.
On configuration A the field Dependent appears all the time and choosing any value for Dependee has no effect
On configuration B it works correctly. When the the standard content entry form is loaded Dependent is not bisible but when I choose one or two it appears.
I have the two configurations set up in Netbeans with the php debugger.
But I'm not experienced with ajax behaviors so I don't really know where to start.

Tokoh’s picture

Tokoh CreditAttribution: Tokoh commented

I think I found my error. You need to use version 1.5 of jquery so modify the jquery settings at least for the administrator and make it use version 1.5.

Tokoh’s picture

Tokoh CreditAttribution: Tokoh commented
Status: Active » Closed (fixed)
Renee S’s picture

Renee S CreditAttribution: Renee S commented
Status: Closed (fixed) » Postponed

Setting to postponed, as jQuery 1.7x support will be needed in the future.

dqd’s picture

dqd
(formerly "diqidoq")
CreditAttribution: dqd as a volunteer and at MAROQQO studios commented
Category: Bug report » Support request
Issue summary: View changes
Status: Postponed » Closed (works as designed)

jQuery future version support should be discussed in another issue. #2 shows off that this is solved. Apart from that:

Thanks for the report and all the efforts in here. But due to inactivity in this issue for some years and because of the upcoming EOL of Drupal 7, I will close this issue on the way by cleaning up the issue queue.

Feel free to re-open as "Needs review" if you found a solution or have a patch to be reported to help others on this outdated version.

If you think this issue or missing feature should be addressed in a newer Drupal core 8 and above compatible version of this project, then please file a new issue to the latest dev.