Unless "Allow conflicts to be added" is checked, you can no longer see Conditional Fields attached to a feature. Existing features, which were previously generated and included conditional fields settings, when you recreate the feature it removes the features[condition_fields] = node:content_type_machine_name entry from the .info. The actual conditional fields feature file with the settings is still there, but it no longer seems to recognize conditional fields. If you check "Allow conflicts to be added", however, it does show up and is already checked off.

Comments

scotself created an issue.

scotwith1t’s picture

scotwith1t
Location Birmingham, AL
CreditAttribution: scotwith1t commented

I don't have the exact details of what's wrong yet, but it seems this is inconsistent. The existing features definitely do NOT list the Conditional Fields that are already packaged up with the feature. Only some times do I have a problem with the line in .info being wiped out. Will post more as I find out.

scotwith1t’s picture

scotwith1t
Location Birmingham, AL
CreditAttribution: scotwith1t commented

It's almost like once I make a change to the conditionals, it tries to then remove that line from the info file next time I recreate the feature? When I do a diff after changing a conditional, I only have the 

- features[conditional_fields][] = node:content_type

entry and no changes to the actual conditionals are captured! Super-bummed as we depend heavily on this module for a large government project! :( Manually updating the conditionals include file for now...