The focal point option isn't in the select on Media images field

Have a content type with a Media image field

you must use a "Media with contextual modifications" instead of native "entity reference" field.

In term of configuration :
1. In the content type, you just need the "media with contextual modifications" field type, and it's configured like a "native entity reference" field type (mainly render mode of the media)
2. In the MEDIA BUNDLE, you need to set :
- in the form mode : use the widget focal_point
- in the view mode (choose in the content_type view_mode) : use the formater "Context crop image" on the field_image, and select a image_style who use the focal crop.

Thanks again!
I am almost there! Only the last step...!
You say:

In the view mode (choose in the content_type view_mode) : use the formater "Context crop image" on the field_image, and select a image_style who use the focal crop.

I get only "Media library extra" :O

A pleasure to learn from you :)

In /admin/structure/types/manage/story/form-display

And one question more.
I used Image field to media → to convert a migrated image field to Media field.
So now I would need another module to make the migration to Media with contextual modifications, wouldn't I?

You say:

In the view mode (choose in the content_type view_mode) : use the formater "Context crop image" on the field_image, and select a image_style who use the focal crop.

I get only "Media library extra" :O

In the view mode configuration of the media image => admin/structure/media/manage/image/display

And one question more.
I used Image field to media to convert a migrated image field to Media field.
So now I would need another module to make the migration to Media with contextual modifications, wouldn't I?

In fact, the module "media_library_media_modify" provide a service to migrate a "standard" reference field to a "Media with contextual" field
Drupal\media_library_media_modify\EntityReferenceOverrideService::migrateEntityReferenceField([entity_type], [field_name]);
So you can use Image field to media to made the "image->ref media" conversion and the service of media_library_media_modify to made "ref media -> media with contextual" conversion

Sorry this morning meetings.
I got it!
but now when I save or delete a selected media I get an error.

Drupal\Core\Entity\EntityStorageException: 'context' not found in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 817 of /var/www/html/donestech10.devel/web/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).

I don't know in which of your modules report this...

Thanks thanks a lot for your patience, you can be a teacher, you know? ;)

Are you sur that the patch on crop ( https://www.drupal.org/files/issues/2023-11-06/%232617818-31-provide_con... → ) has passed ?

mmm how do I know?

in media_contextual_crop I don't see a patch...
do I put it in my composer.json?

run a composer reinstall drupal/crop

you may have a

  - Installing drupal/crop (2.3.0): Extracting archive
  - Applying patches for drupal/crop
    https://www.drupal.org/files/issues/2023-11-06/%232617818-31-provide_contextual_capability_to_crops.patch (provide_contextual_capability_to_crops)

patch applied, cleared the registry and I keep with the error.
Maybe I have to create the field again?

can you check the database, if the field exist in "crop_field_data" table ? if it's it may be a bug in your code...

The website encountered an unexpected error. Try again later.

Drupal\Core\Entity\EntityStorageException: 'context' not found in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 817 of core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).

Drupal\Core\Entity\Query\Sql\Tables->addField() (Line: 58)
Drupal\Core\Entity\Query\Sql\Condition->compile() (Line: 176)
Drupal\Core\Entity\Query\Sql\Query->compile() (Line: 81)
Drupal\Core\Entity\Query\Sql\Query->execute() (Line: 177)
_media_contextual_crop_field_formatter_get_crops_from_entity_field() (Line: 91)
media_contextual_crop_field_formatter_entity_update()
call_user_func_array() (Line: 409)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}() (Line: 388)
Drupal\Core\Extension\ModuleHandler->invokeAllWith() (Line: 416)
Drupal\Core\Extension\ModuleHandler->invokeAll() (Line: 217)
Drupal\Core\Entity\EntityStorageBase->invokeHook() (Line: 900)
Drupal\Core\Entity\ContentEntityStorageBase->invokeHook() (Line: 564)
Drupal\Core\Entity\EntityStorageBase->doPostSave() (Line: 781)
Drupal\Core\Entity\ContentEntityStorageBase->doPostSave() (Line: 489)
Drupal\Core\Entity\EntityStorageBase->save() (Line: 806)
Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (Line: 352)
Drupal\Core\Entity\EntityBase->save() (Line: 270)
Drupal\node\NodeForm->save()
call_user_func_array() (Line: 129)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers() (Line: 67)
Drupal\Core\Form\FormSubmitter->doSubmitForm() (Line: 597)
Drupal\Core\Form\FormBuilder->processForm() (Line: 325)
Drupal\Core\Form\FormBuilder->buildForm() (Line: 73)
Drupal\Core\Controller\FormController->getContentResult() (Line: 39)
Drupal\layout_builder\Controller\LayoutBuilderHtmlEntityFormController->getContentResult()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 627)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 181)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 58)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 704)
Drupal\Core\DrupalKernel->handle() (Line: 19)

Yes, the field crop_field_data exists in the database.

the fields:
cid
vid
type
langcode
entity_id
entity_type
uri
height
width
x
y
default_langcode
revision_translation_affected

Can you make a

drush fbi crop

did you see the "context" field too ?

Second question : did you have some crop already saved ?

"crop_field_data" is a table, not a field ... and it seems there is no "context" (data)field in it.

drush fbi crop
------------------------------- ---------- ------------------ -------------
Field name Required Field type Cardinality
------------------------------- ---------- ------------------ -------------
cid integer 1
uuid uuid 1
vid integer 1
type entity_reference 1
langcode language 1
entity_id integer 1
entity_type string 1
uri uri 1
height integer 1
width integer 1
x integer 1
y integer 1
context string_long 1
revision_timestamp created 1
revision_uid entity_reference 1
revision_log string_long 1
default_langcode boolean 1
revision_default boolean 1
revision_translation_affected boolean 1
------------------------------- ---------- ------------------ -------------

I don't have crops saved because the error...

I go to delete de field and make it with a different name.

The same.
I have in the Media type image crops saved.
I go to try to create a different one in case that it is that.

did you have some message in "/admin/reports/status" page about entity ?

because, it seems the field are known in the registry, but not present in database ...

I have made a new crop and a new field but still have the problem.
I go to make it in a fresh install.

the bug are you table crop_field_data doesn't have the "data field" context even the entity registry have it.

in fact, you don't need to try to create a field or a crop, as long as the Crop module is activated, the patch apply and the table does not contain the field, it won't work.

But why does the context data field is not created? how can I solve that?

It can be the most obvious and stupid reason : did you have made an drush updb after the patch apply ?

glups... I am ashamed ....
I have done drush updb and we have the field and CAN SAVE!!!!
I am very tired and I forgot... thanks for the patience.

And the last thing, how do I assign the different styles, I go to the /admin/config/media/responsive-image-style , don't I?

The main way (node -> media -> image -> style) :

- In the node "view mode" you choose the "view mode" it will be used for the media
- In the media "view mode" you choose (for the image field) the formater "contextual image crop" with the image_style you have set to use a crop (focal point / manual crop).

The responsive image way ( node -> media -> responsive image -> styles) :

Responsive image is something else, it permit you to configure some "break-point" and determine which "image style" using in each break-point (I didn't explain you how configure a responsive-image-style).
- In this case, in the media "view mode" you will choose the "Responsive image" formater and the "responsive_image_style" you have set.

Thank you. If you come to Barcelona, I will cook a paella for you :)

I know break-points with the breakpoints module that now is responsive images from D7.
Now I am confused with the crop entity.
With the main way (node -> media -> image -> style), how do I assign the image style for each break-point so with the focal point configuration the images for each are created?

In the "normal way", there isn't have break-point. The image (in the media) are render use a single style.

If your need are to use break-points (in ordre to rendre the image in mulitple style), you need use Responsive-image module.