Warning: key() expects parameter 1 to be array, null given in Drupal\entity_browser\Plugin\Field\FieldWidget\EntityReferenceBrowserWidget::processEntityBrowser()

Patch #12 also works for me. My problem case was adding a paragraph to a content type that had another paragraph within it. This has solved the issue.

This bug surfaced when switching the widget from Entity browser to Autocomplete for an unlimited Entity reference taxonomy field. No problem making the switch, but when reloading the node form display, the page fatals. Patch #12 → get the node form display printing again.

comment #19 helps me - resaving the widget in the manage form display

I'm not sure why this is RTBC. One of the maintainers and I both said it should be handled different than the current patch.

To be extra clear, both lines of the processing function need to be inside the if statement to avoid triggering additional bugs.

+++ b/src/Plugin/Field/FieldWidget/EntityReferenceBrowserWidget.php
@@ -466,7 +466,7 @@
     $element['#attached']['drupalSettings']['entity_browser'][$uuid]['selector'] = '#' . $element['#custom_hidden_id'];

This line also needs to not run with an invalid id.

This should be a simple re-roll.

I have fixed the issue using patch #12
Version: 8.x-2.9
PHP: 8.1.20

Patch # 12 works great to me:

- Drupal 10.1.2
- PHP 8.1.5
- Entity Browser 8.x-2.9

Just ran into this myself, similar to #11 it was due to an old, broken field type/widget. Thought I might as well implement what has been asked for and ignored a few times 😅

I've tested patch #25 and it is working for me. Thank you all:)

Would be great if this could be merged!

The patch also works for me! Thanks

this should wrap the whole thing in an if statement and possibly also log a warning or something, because the only reason for this that I can see is misconfiguration

I still don't see this being addressed in the latest version.

chetan 11 → made their first commit to this issue’s fork.

MR 37 looks good

Per #29 we need to log a warning.

Re-rolling patch for version 8.x-2.10

What's the difference between this issue and https://www.drupal.org/project/entity_browser/issues/3437293 🐛 Entity Browser widget does sets a value of null for entity_browser by default Needs work ?

Looks to me like this bug, 3437293, and 3277056 are all the same, and each has patches available which (approximately) do the same thing. Of the myriad of patches available, I'm trying https://www.drupal.org/files/issues/2024-06-12/2914385-35.patch → because that seems to be the simplest (smallest LOC) that doesn't generate an empty-string UUID. But I really don't know which patch is better, honestly.

This is potentially duplicate issue mentioned in #37 - https://www.drupal.org/project/entity_browser/issues/3437293 🐛 Entity Browser widget does sets a value of null for entity_browser by default Needs work

I had the same issue with one of my fields. Re-saving the field as per comment #3 fixed the issue for me.