I have the need to changed the availability of fields within one set of field collection. As an example a user adds a new filed collections set containing a field called type which allows a radio button selection between selectable or custom.

The selection of selectable hides the "custom field" and un-hides the "select list" control.
The selection of the option custom hides the "select list" control is hidden and un-hides the "custom field".

Of course the addition of another field collections set would not be affected by the earlier choices.

Comments

drupov’s picture

I have created a similiar issue over at the field_collection module: http://drupal.org/node/1252886

Not really sure where this request would belong to.

peterpoe’s picture

Status: Active » Fixed

I wasn't aware that Field collections dependencies had stopped working. Anyway, I committed a big patch
two days ago that broke them in a completely unrelated way, then fixed the problem here:
#1263278: Last update made field_collection fields disappear
Way of fixing things :)
Anyway, I'm marking this as fixed.

drupov’s picture

Status: Fixed » Active

Sorry, opening this issue again.

#2 fixes conditional states in field collections (yeah!) but:

If you have field collections that can have more than one value, after adding a next item (an additional set of fields) the functionality breaks for that next item - the dependent field is visible regardless of the state of the dependee field.

For the first item of the field collection the functionality of conditional fields is still intact though.

peterpoe’s picture

Status: Active » Fixed

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

Status: Fixed » Closed (fixed)

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

Chris Pergantis’s picture

We are currently having one small issue concerning the initial editing of a field collection when using conditional fields. Upon opening the edit, either an insert or a change, the conditionals are not being set based on the field that is in control. It actually takes a couple of selection changes to get the conditionals in sync with what is expected. This seems to be the only issue we have located. We will look at this next week see if a patch can be provided... actually Ben Coleman will be doing the development.

Great module thanks for all the work!

bryancasler’s picture

@cperg was Ben able to solve this?

Chris Pergantis’s picture

@animelion sorry just got this - I will check to see how we resolved the issue back in 2011 - should be able to reply to your inquiry by next Tuesday.

bryancasler’s picture

Thanks cperg, no rush. I found another way of implementing a solution for my current project, but I would still be interested in this for future work.

ydnar79’s picture

Animelion may not be in a big rush for the solution. But I for one would be greatly interested in a way to make it work. I am currently working on a project in which this would be immensely helpful. So any information you can share would be appreciated.

Rhodungeon’s picture

Same for me! It would be great if Animelion tell us about the alternative solution.

bryancasler’s picture

@Rhodungeon, this alt. solution won't work unless you were trying to do exactly what I was trying to do. I'm using the NodeConnect module.

SocialNicheGuru’s picture

@animelion, I am using node connect and would love to know your solution.