Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.e.g. (this is from a real-world client example!) if there was a form that only showed fields that contain values, but added a custom element to specifically add further fields to the form(s). That would need to show on both the shared and translation forms. (Although should that itself be smarter to only add translatable fields on translation forms; and untranslatable ones on the shared forms maybe?!)
Comments
Comment #2
james.williamsThat real-world example actually uses https://www.drupal.org/sandbox/jamsilver/field_attach_form_selective, not a custom element. We could still add some kind of 'opt-out' to the separation; e.g. support some a property on elements like
'#etssef_all_forms' => TRUE, which that could use.That particular use case may still need to adjust its own implementation as well, as suggested, but that's a separate issue.
Comment #4
james.williams