Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This is exactly the similar bug for 2.0 version on lines of https://www.drupal.org/project/jsonapi_file/issues/2980653 .
While creating the new content it gives ERROR 500 but also creates the content.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | skip-entity-null_v2-0_3019329-1.patch | 811 bytes | npralhad |
Comments
Comment #2
npralhad commentedPushed the patch. Is based on https://www.drupal.org/files/issues/2018-06-07/skip-entity-null_2848419_...
Comment #3
wim leersThis sounds like it's exactly the same as #3014380: EntityReference base fields that are optional are not empty, but its sole item is empty, causing EntityReferenceFieldNormalizer to fail.
Can you please confirm that in your case, you're also using an optional entity reference base field? Please apply either the patch there or update to
8.x-2.xHEAD.Comment #4
wim leersLinking the issue mentioned in the original report.
Comment #5
wim leersComment #6
wim leersThis still needs steps to reproduce.
BTW, it's not cool to cross-post a patch from here to #3014380-35: EntityReference base fields that are optional are not empty, but its sole item is empty, causing EntityReferenceFieldNormalizer to fail without explaining why, especially since that issue is already fixed.
Comment #7
wim leersClosing because >2 weeks without providing steps to reproduce. Feel free to reopen when you have steps to reproduce!