Problem/Motivation
There is an issue when using Inline Entity Fields (doesn't seem to matter which kind but I used complex) in a paragraph field attached to a node that has a cardinality greater than one, in which the paragraph (which uses an Inline Entity Form) has a field that has a required media (in my case, image) reference field. If you enter in the required fields, and either try to preview the node, or collapse the paragraph form, an error occurs where EVERY field in the paragraph that contains a media reference will be labelled with an "This Value should not be null" error.
It should be noted this occurs when the form actually should validate. For example, if said paragraph has the media field set as required and you do NOT enter a file for the field, it will correctly display an error on the media field saying that field is required. Its only when all other validation seems to succeed that this particular issue happens. The "This value should not be null" error also seems to appear for every single field, including fields that are not full.
You can see an example of this in the screenshot I uploaded.
Steps to reproduce
I was able to replicate the issue using the following https://simplytest.me/ configuration:
- Drupal 10.2.9
- IEF module
- Field Group Module
- Paragraphs
Field Group I used to try to get a clean drupal install that is as close to my specific situation as possible. May not be necessary to replicate the issue.
After Installation, log in and then:
- Enable Media module
- Create new paragraph type with a entity reference to a media item (choose image)
- Make this media item required in field settings
- Create new content type that has a paragraph field for newly created paragraph type. Choose cardinality of unlimited
- Set up form display so the new field is in its own tab (may not be necessary)
- Create new node of that type
- Add an image paragraph to field. Add everything required.
- Click collapse button. The "This value should not be null" error will appear
- Clicking the Preview button should also cause this error to happen.
I did research this issue a bit before posting this, there are a couple related issues that seem to cover this, but don't seem to solve the problem, and have a few differences in context that I figured I should create a new issue, especially since most related problems are for different versions. If I was mistaken and should have added to those other issues, please let me know.