Unable to install due to unmet dependencies.

Hi AgathaCrystal

I tried to replicate this on a Vanilla Drupal 9.5 and 10 but it's working for me when I install the module via

$ composer require drupal/ckeditor_media_resize
$ drush en -y ckeditor_media_resize

and also when I install via UI. Could you please share a screenshot of your module folder? The folder ckeditor_media_resize/config/install would be particulary interesting.

My media type image was not called "image" but called "media_image". So I had updated 4 files in "ckeditor_media_resize\config\install" core.entity_view_display.media.image.cke_media_resize_*.yml (*large, small, medium and xl) dependencies: config:

Original
- field.media.image.field_media_image

- media.type.image

My modification
- field.field.media.media_image.field_media_image

- media.type.media_image

Once i made the change on all 4 files it started working

For me it was sth. different still. I'm afraid it won't work reliably this way. Reason:

/admin/structure/media/manage/image/fields

Note that the fields here are freely configurable. Including their machine_name. This module should work (or even install) no matter what configuration you have IMHO.

Same here:

the medias image field's names are customised.

So, I get this on install:

Unable to install Ckeditor Media Resize due to unmet dependencies: core.entity_view_display.media.image.cke_media_resize_large (field.field.media.image.field_media_image, media.type.image)

We need to add some basic test coverage for the basic setup process to make sure it works, then we'll be able to work through edge scenarios.

Sorry for coming back so late - I settled for a different approach and forgot.

As in #4 & #5 described, I have custom media types and don't even had the media type 'image' in the first place. I think if Drupal is installed in the barebone version, the media type wont get created. My page is running now with D10 and also has the problem (ofc).

Same issue here, so I don't think we should see this as edge-case. The module makes assumptions that don't seem to match for several installations.

Added an EXAMPLE how to manually fix this for different media image field names! In our case this for example is named field_image. The MR isn't going anywhere, it just shows a manual resolution.

TBH I have no good idea yet, how this could be solved in general. Perhaps this part of the install config could be moved into optional, so the module still installs, if the dependencies are not met? But then I think we'll see issues about the module not working as expected?

Well, AFAIU the "problematic" part tries to configure certain things for the existing media library image fields on install. I think this should just be omitted completely and users should instead by instructed to configure things themselves. I haven't even fully understood yet what exactly it is that would so sorely be missing if we just left that stuff out altogether. If we really want to keep this, then, I guess, we can't make it work with a simple static YML file. It's just not flexible enough. We'd have to run PHP code on install that looks for an image field etc. But, as I said, I don't think it's necessary. Just install the module without all that install-o-magic and let users configure their fields as they deem fit.

Is there any hint on how to solve this?

Running latest Drupal 10.2.3, freshly installed, and have the same error.

The problem is important, but in any case, the configurations with some unstable dependencies must be placed in the "optional" directory. It would unlock the possibility of using this module with some other fields configuration and as a part of some profile installation