- 🇺🇸United States sim_1
This works to substitute a title, but I still end up in a bad state. The form validation works when creating the H5P is in a unique form, but when it's within a multi-value field it fails. For example, we have it as a media item that can be added in a multi-value field and that submit/save button (for the field) isn't recognized in the same was as the whole entity submit button.
- 🇺🇸United States sim_1
Is there a better way to detect what type of form (single value field form within a node vs media vs multivalue field etc) it is and therefore intercept the form validation more universally there?
- 🇺🇸United States maya maier
Do you have repro steps/configuration for this issue? I'm unclear on the context where this would be submitted through AJAX.
- 🇺🇸United States sim_1
Yes, this particularly happens when H5Ps are being added within a multi-value field. This means that the field to add an h5p exists within a node/entity form. The node validation and the h5p form validation aren't speaking well to each other.
- First commit to issue fork.
- Merge request !49H5P Editor submit handler now checks if an event exists during trigger to... → (Merged) created by msandoval