Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After following the instructions listed here on how to create a video selection widget for Brightcove videos, I receive this error after selection the Brightcove field:
https://pronovix.com/blog/brightcove-video-connect-drupal-8-part-4-inclu...
The website encountered an unexpected error. Please try again later.
Drupal\Core\Config\ConfigException: Used entity browser selection display cannot work in combination with settings defined for used selection widget. in Drupal\entity_browser\Form\EntityBrowserForm->isFunctionalForm() (line 161 of modules/entity_browser/src/Form/EntityBrowserForm.php).
Drupal\entity_browser\Form\EntityBrowserForm->buildForm(Array, Object)
call_user_func_array(Array, Array) (Line: 514)
Drupal\Core\Form\FormBuilder->retrieveForm('entity_browser_brightcove_video_browser_widget_form', Object) (Line: 271)
Drupal\Core\Form\FormBuilder->buildForm('entity_browser_brightcove_video_browser_widget_form', Object) (Line: 74)
Drupal\Core\Controller\FormController->getContentResult(Object, Object)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 574)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
call_user_func_array(Object, Array) (Line: 144)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 64)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 57)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 99)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 78)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 50)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 656)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)
Comments
Comment #2
jaydee1818 CreditAttribution: jaydee1818 commentedComment #3
marcoscanoAre you sure the settings for your browser are correct? This error normally appears when there is a misconfiguration somewhere (for example if you are using a "NoDisplay" or "View" selection display when you are expected to be using the "MultiStepDisplay" one).
Can you please share steps to reproduce the error? (and/or your browser config export)
Thanks!
Comment #4
jaydee1818 CreditAttribution: jaydee1818 commentedSee the link I posted in the original post? That outlines detailed steps on how to configure and I followed them exactly. You will reproduce if you also follow. Cheers.
Comment #5
steveedson CreditAttribution: steveedson commentedWe're also getting the same issue.
We have "No Selection Display" set, and "Automatically submit selection" enabled. This causes the error shown above. If I disable "Automatically submit selection", the page loads, however I cannot select any images.
Comment #6
PapaGrandeI am seeing the same issue as @steveedson, where even with "Automatically submit selection" disabled, no images can be selected. This makes the entity browser unusable.
Comment #7
PapaGrandeThis may be a duplicate of #2853751: Selecting "Automatically submit selection" in widget plugin view leads to error.
Comment #8
PapaGrandeFor now, the workaround seems to be to use "Multi step selection display" for "Selection display plugin" under the General Information tab AND enable "Automatically submit selection" on the Widgets tab. However, this allows the user to select multiple items even when the field is limited to one value, a confusing UX for content editors.
Comment #9
PapaGrandeComment #10
modulist CreditAttribution: modulist commentedI'm also seeing the same issue with version 8.x-1.0. The workaround I used was to revert to the image widget until the entity browser issue is resolved.
Comment #11
dkre CreditAttribution: dkre commentedHaving the same issue but only when used in combination with Entity Embed.
#8 workaround seems to be the go at the moment.
Comment #12
szeidler CreditAttribution: szeidler at Ramsalt Lab commentedI also ran into the problem and #8 is a good workaround for now, although it requires one additional action by the content manager and is a bit confusing.
It seems that the problem was somehow introduced in #2822009: Improved MultiStep selection display
Comment #13
ksavoie CreditAttribution: ksavoie commentedJust came across this same issue. : (
Comment #14
ecoluke CreditAttribution: ecoluke commentedSame issue - #8 as temp workaround worked for me.
Comment #15
glass.dimly CreditAttribution: glass.dimly commented#8 doesn't work for me as a workaround because it allows the selection of multiple entities and the reason why I want to autosubmit is because I want to limit it to single-entity select.
Comment #16
AaronBaumanJust hit this myself, and #8 resolved the issue (after i ran into the helpful "entity browser select form field not found in the view" error message).
Ideally, if the configuration were incompatible, then I should hit it at the configuration step - not at the node edit step.
In practice, i imagine that's probably pretty difficult to implement...
Is there an issue open for this already?
Comment #17
emb03 CreditAttribution: emb03 commentedHaving this issue too. Automatically submit on select is not working. Please fix ASAP. Stuff like this is what gives Drupal a bad name.
Comment #18
ChrisRuczak CreditAttribution: ChrisRuczak commentedSame issue here. Anyone find a fix?
Comment #19
Gil'BarbareSame issue again. Is there a way to fix it please or a working workaround?
Comment #20
alienzed CreditAttribution: alienzed commentedThank you for all the hard work put into wonderful modules like this, but I am also experiencing this issue and agree that it gives Drupal a bad name, perhaps underservedly. My client asked me today after reporting yet another bug with Entity Embedding.
"How can Drupal not have this kind of problem solved?"
It should not be possible to configure the component in a way that crashes pages. :/
Comment #21
oknateI'm new to helping maintain Entity Browser. I'm working on making it more user friendly. You can help out by helping to test issues marked as "Needs Review". For example: #2930677: Validate widget entity type and bundles, which is another issue related to misconfiguration problems crashing pages.
I will investigate this issue and see if I can come up with a fix. Thanks for being patient. Entity Browser will improve!
Comment #22
DuneBLI confirm the bug... #8 is not a solution for my use case
Comment #23
rwilson0429 CreditAttribution: rwilson0429 commentedDisabling "Automatically submit selection" on the widget plug-in form (admin/config/content/entity_browser/[YOUR ENTITY BROWSER]/widgets?js=nojs) works for me.
Comment #24
ph7 CreditAttribution: ph7 commentedI can confirm #23 works for me