I would like to add that this seems to be a prevalent issue - I see it with 2 content types - one that references the other (in my case - a 'photoset' content entity and 'photo-with-metadata' content type - where the first can have one or more photos attached. Since the new entity reference hasn't been saved or even built - the 'Value should not be null' message is thrown.
It is worth pointing out that once one entity has been saved (since it is required) - I no longer gets the message when trying to add and preview a second (in my case photo) - however of course - the second photo isn't part of the preview.
So I think the larger issue is that in fact - preview simply doesn't work for inline entity form. I don't know if there is some Drupal magic that could get this to work.
I should mention - this module is fantastic and I use it on multiple sites and makes complex content creation possible.. Thanks!
This also happens when setting restrictions on content-type - then views (request path) no longer get tagged.
The passesConditions logic seems to be implementing an 'and' condition - as in ALL configured conditions have to pass - so this feels like are larger issue in how conditions are evaluated and in which context.
This is drupal 10.4 and GT 2.0.8
I wonder if this would also be fixed by: https://www.drupal.org/project/simple_image_rotate/issues/3317110 🐛 simple_image_rotate_rotate_image isn't idempotent RTBC - making simple_image_rotate idempotent.
This patch worked for me .. Thanks!
It should be noted that since this causes an exception it stops further JS parsing - which when using aggregated JS means that many other JS libraries may not be loaded - so the effect may be far removed from tables.
re PHP 8.1 - no comment - I moved to PHP8 many months ago with no issues. Moving to D10 will take another few months as there are still modules we use that aren't quite ready.
FYI - this module is awesome and a critical part of one of our workflows for adding research publications with articles and authors - so we have 2 levels of inline forms... Thanks for all the hard work...
I noticed this PR: https://git.drupalcode.org/project/inline_entity_form/-/merge_requests/103
which implies that the 3.x branch once released wont support drupal 9. I think it is very important to let folks know that this is
an additional reason to downgrade to 1.x rather than up to 3.x. Obviously many many of us aren't at drupal 10 yet.
Thanks...