Many implementations of \Drupal\Core\Plugin\PluginFormInterface assume they are used as top-level forms because of the fact they call FormStateInterface::getValue() directly rather than getting the value from the form's state based on the plugin form's position in the parent form. This requires using NestedArray and $form['#parents'].
This works fine in core because most plugin forms are only used in one single way, but this obviously fails when embedding plugin forms in different parent forms. This is exactly what Plugin → does.
PluginFormInterface's documentation to explicitly state that plugin forms are meant to be embedded, and that the $form parameters only contain the plugin forms' elements. See
#2532970: PluginFormInterface must document $form means the plugin's own elements →
.PluginFormInterface's documentation to explicitly state that plugin forms are meant to be embedded, and that extra measures must be taken to reliably retrieve submitted form values. See
#2537732: PluginFormInterface must have access to the complete $form_state (introduce SubFormState for embedded forms) →
.Find all broken implementations and create separate issues for them.
None.
None.
None.
Fixed
10.1 ✨
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There is one issue child left in this Meta. We have a practice of allowing metas to be closed when there is only one remaining item. I am doing that now.
This is also not a bug report, I am changing it to a plan.
Automatically closed - issue fixed for 2 weeks with no activity.