After upgrading to field-collection-7.x-1.0-beta12 from a previously patched version supporting entity-translation, I've come across this weird issue. Tested with dev and same results.

When a text field (translation enabled for this field) inside a field-collection (translation disabled) is required, it never pass validation and is always considered empty even if there is data inside this field.

Narrowed it to this function (field_collection_field_widget_embed_validate) which seems to be missing something when entity_translation is enabled.

Any one encountered similar behavior?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

letrotteur created an issue. See original summary.

daniel.delaiglesia’s picture

Hi letrotteur,

I encountered with this behavior. I've create a patch to apply.
I hope it helps you.

Regards

james.williams’s picture

Status: Active » Closed (duplicate)
Related issues: +#2948391: Field is required error

I ran into this a while ago too, and created a patch which I think better reflects the intention of the code: #2948391: Field is required error.