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.Hi there. Unfortunately, I'm experiencing all kinds of issues with Entity Browser. The Drupal log shows me this message over and over again.
Location http://example.org/admin/config/content/entity_browser/browse_images/wid...
Message Drupal\Component\Plugin\Exception\PluginNotFoundException: The "media_bundle" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 133 of /home/user/drupal8/core/lib/Drupal/Core/Entity/EntityTypeManager.php).
I'm running Drupal 8.2.1 with:
- Entity Browser 8.x-1.0-alpha9
- Entity Embed 8.x-1.0-beta2
- File Entity Browser 8.x-1.0-alpha1
In the past, some media related modules may have been installed/deinstalled, but I don't know if that's relevant. Please let me know if you require more details.
If anyone could point me in the right direction, I'd be grateful.
| Comment | File | Size | Author |
|---|---|---|---|
| #20 | 2820183-20.patch | 2.13 KB | sharif.elshobkshy |
| #19 | 2820183-19.patch | 2.08 KB | sharif.elshobkshy |
| #16 | 2820183-16.patch | 1.66 KB | Primsi |
Comments
Comment #2
P44T CreditAttribution: P44T as a volunteer commentedComment #3
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedI'm having this issue too.
We do need to have Media types first.
Comment #4
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedPlease check if you have media_entity module enabled.
Comment #5
P44T CreditAttribution: P44T as a volunteer commentedCurrently, I don't have it installed or enabled. Would I have to install it? I can't find it as a dependency of Entity Browser in the documentation...
I don't need the entire media stack, as it is an overkill for my situation. I was just using File Entity Browser to embed images into node content. This project has Entity Browser and Entity Embed as dependencies and suits my requirements just fine.
Comment #6
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedNo it is not, but you must have installed/used something that needs it and doesn't provide dependencies. Which modules are you using along the Entity browser?
Comment #7
P44T CreditAttribution: P44T as a volunteer commentedHere is the list of enabled modules:
List of all modules:
Comment #8
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedCould be DropzoneJs. That module provides two entity browser widgets; one that works with files and one that works with media entities. Make sure that you use the first one.
Comment #9
P44T CreditAttribution: P44T as a volunteer commentedPerhaps this has been the case, although I'm fairly sure I would not select 'Media Entity DropzoneJS', just because I know I'm not using Media Entity.
Anyway, I found when the issue occurs in my environment. It happens when I go to the 'Widgets' page when editing a certain entity browser I configured earlier on. I extracted the configuration of the faulty entity browser from the config table in the database:
a:13:{s:4:"uuid";s:36:"04da9c8a-311b-44f1-8308-05e14fbe288b";s:8:"langcode";s:2:"nl";s:6:"status";b:1;s:12:"dependencies";a:1:{s:6:"module";a:1:{i:0;s:20:"dropzonejs_eb_widget";}}s:4:"name";s:13:"browse_images";s:5:"label";s:13:"browse_images";s:7:"display";s:10:"standalone";s:21:"display_configuration";a:1:{s:4:"path";s:21:"/browser/afbeeldingen";}s:17:"selection_display";s:10:"no_display";s:31:"selection_display_configuration";a:0:{}s:15:"widget_selector";s:4:"tabs";s:29:"widget_selector_configuration";a:0:{}s:7:"widgets";a:1:{s:36:"1a9c11c9-268e-4ef9-bbf9-9d2a59f68617";a:5:{s:8:"settings";a:5:{s:15:"upload_location";s:40:"public://[date:custom:Y]-[date:custom:m]";s:20:"dropzone_description";s:30:"Drop files here to upload them";s:12:"max_filesize";s:2:"2M";s:10:"extensions";s:52:"jpg jpeg gif png txt doc xls pdf ppt pps odt ods odp";s:11:"submit_text";s:15:"Select entities";}s:4:"uuid";s:36:"1a9c11c9-268e-4ef9-bbf9-9d2a59f68617";s:6:"weight";i:1;s:5:"label";s:10:"dropzonejs";s:2:"id";s:10:"dropzonejs";}}}Does this show anything, or would I need to provide additional information?
Comment #10
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedIt could be that the Media entity widget that Dropzone provides causes this when Media entity is not enabled. There are some dependency problem that we experienced in the past in this area. Could be related to that.
Comment #11
marcoscanoI can reproduce a related bug (not sure if it is exactly what happens to you though, but it can be the same :)
Steps to reproduce on a clean install:
- Enable the modules DropzoneJS, DropzoneJS Entity Browser, Entity Browser and Ctools
- Go to
/admin/config/content/entity_browser/addand create an EB, select anything for the 4 first steps- On the last step (Widgets), select "DropzoneJS", which will work fine, and then select "Media Entity DropzoneJS". At this point nothing happens, and you may think "ok, this is not available, let's leave then only the first one".
- Save the form.
- WSOD, with the same message on the log:
Some information from the non-available plugin is indeed saved into the entity_browser, because it is completely broken trough the UI, if I try to edit the widgets again I always get the WSOD, the only solution is to delete the browser and recreate a new one.
Perhaps this could be solved in a more generic way if the plugins declare their dependencies somehow, and in Entity Browser, instead of adding all of them:
we would add only the ones with dependencies satisfied?
Comment #12
Primsi CreditAttribution: Primsi for Examiner.com commentedThis is relevant then: #2769771: Split Media Entity specific widget off the "DropzoneJS entity browser widget" sub module
I am still not sure if that's the correct approach. The alternative could probably some kind of soft dependency, ie: check if medi_entity exists where relevant and return some kind of notification about the missing dependency.
Comment #13
P44T CreditAttribution: P44T as a volunteer commentedmarcoscano, thank you for the clear explanation. I think the situation you describe is very likely to have happened to me.
Comment #14
peter.keppert CreditAttribution: peter.keppert commentedPlease note that this error message may also appear in case described in #2897255: Support Media core module (Drupal core 8.4.x-dev). The same error manifests itself, but causes are different.
Comment #15
rsavage CreditAttribution: rsavage commentedI just hit this issue, how exactly can I resolve it?
Comment #16
Primsi CreditAttribution: Primsi at MD Systems GmbH for Examiner.com, MD Systems GmbH commentedLet's try a Berdir's suggestion. Also moving to 8.x-2.x and make this a bug.
Comment #17
lias CreditAttribution: lias commentedIs this similar error issue, re "media_bundle should be media_type?"
Media video entity: https://www.drupal.org/project/media_entity_video/issues/2930974
Comment #18
heddnI still get
Drupal/Component/Plugin/Exception/PluginNotFoundException with message 'The "dropzonejs_media_entity" plugin does not exist.'after applying this patch.Comment #19
sharif.elshobkshy CreditAttribution: sharif.elshobkshy as a volunteer commentedHi,
I tried patch #16 and did not work.
I don't know if this is the best way to solve the issue, but it got me out of the hole.
Basically it gives you the chance to access the "Widgets" page and delete the Plugin that causes the fatal issue (in my case, "Media Entity DropzoneJS").
Ideally we should prevent the option from showing up on the UI under certain circumstances (but I'm not sure which ones they are).
Comment #20
sharif.elshobkshy CreditAttribution: sharif.elshobkshy as a volunteer commentedPatch updated for dropzonejs 2.3