Looks like all related issues are marked as closed (fixed), so I am sot sure if this is a seperate issue or was never properly fixed.

Conditional Fields 7.x-3.x-dev 2011-Sep-13
Field collection 7.x-1.x-dev 2011-Sep-27

See the attached image for a visual description of the problem.

The first field collection works as expected, however, conditional fields has no effect on additional field collections.

Comments

ironbuilt’s picture

I second this. This would be awesome if it could be supported.

cyxair’s picture

Subscribing !

charlie-s’s picture

Same here. I was assume this was occurring because the IDs change for all elements when ajax forms are used, but in reality it looks like the first element is the only one that the outputted javascript ever looks for.

Matt Townsend’s picture

Subscribing.

It doesn't seem to matter if the field is set to a limited number of values or unlimited - only the first collection is processed.

drupov’s picture

Any progress made here?

Can we have at least a hint where work on this can be started?

charlie-s’s picture

I just threw in some JavaScript to do the same thing until this is fixed.

<?php
  // Hide 'em on page load.
  $('#edit-field-field_collection_name .field-name-field-field_name .form-checkbox').each(function() {
    if ($(this).is(":checked")) {
      $(this).closest('tr').find('.field-name-field-other_field_name input').show();
    } else {
      $(this).closest('tr').find('.field-name-field-other_field_name input').hide();
    }
  });
  // Hide 'em when conditional checkbox is clicked.
  $('#edit-field-field_collection_name .field-name-field-field_name .form-checkbox').click(function() {
    if ($(this).is(":checked")) {
      $(this).closest('tr').find('.field-name-field-other_field_name input').show();
    } else {
      $(this).closest('tr').find('.field-name-field-other_field_name input').hide();
    }
  });
?>
benmalen’s picture

I'd love to get the ball rolling on this issue. What's needed? I'm willing to pay for a fix.

bryancasler’s picture

Re-posting this message from the module's maintainer

We don't support multiple value fields yet.
You can follow this issue for updates on this feature:
#262453: Grouping dependencies by dependent with OR/XOR evaluation

bryancasler’s picture

Status: Active » Closed (duplicate)

Does anyone have a grasp on how much work would actually be involved to get this working?

john morahan’s picture

I don't see how this is a duplicate. That issue is about multiple fields controlling a single field. This one is about dependencies between fields within a field collection, which are not working when additional deltas of the field collection are added.

bryancasler’s picture

Status: Closed (duplicate) » Active

I'm not really sure how that got switched, not intended at all. Sorry for the confusion.

Rhodungeon’s picture

Subscribing... Allowing these two modules to cooperate would be so important!!

bryancasler’s picture

I'm placing a bounty of $100 to resolve this. Additionally, I'll match dollar for dollar the first $50 in pledges from other users.

*Is this the right place to post a bounty or should it be placed elsewhere? Should [bounty] be added to the issue title?

Rhodungeon’s picture

I'll add $ 20 to the bounty if someone resolves...

bryancasler’s picture

What I'm trying to accomplish with Conditional Fields will most likely be solved by another model. For that reason I am removing this bounty.

Ref: #1067308: Integration with field_collection

larsmw’s picture

Hi,
What is the status of this issue? I have the same issue as OP. Is it this module thats "broken" or is the problem in field_collection?

tejaspmehta’s picture

Subscribing

swarad07’s picture

Any updates on this issue ?

bryancasler’s picture

peterpoe’s picture

Duplicate of #1464950: Support for multiple "Field collection" and "Multifield" fields.
(this was posted earlier but work is going on there)

peterpoe’s picture

Status: Active » Closed (duplicate)