Add hook_entity_translation_access()

Thanks Marc, this seems to make sense to me as well. It will definitely need tests. But first let's see if this is something that should be added.

+++ b/core/modules/content_translation/src/ContentTranslationHandler.php
@@ -252,7 +252,16 @@ public function getTranslationAccess(EntityInterface $entity, $op) {

@@ -252,7 +252,16 @@ public function getTranslationAccess(EntityInterface $entity, $op) {
+    $access = \Drupal::moduleHandler()->invokeAll('entity_translation_access', [$entity, $this->currentUser]);

One thing for now, it might be good to pass the operation to the hook as well.

This needs tests, probably an integration test is sufficient.

#3018576: Content translation should allow for a language-aware access checks deprecates getTranslationAccess() which means this issue can't make it into core if so.
Please use #3056020: Content translation access control to agree on an implementation plan.

Reroll for 9.1.x

I'd rather not see a new hook, but what I suggested in #3056020-8: Content translation access control. It would make it far easier for the Group module to support translation access and would allow us to remove most of the hard-to-alter route access check logic in favor of calling $entity->access('update translation', $account, TRUE)

Edit: But until we can actually work on such a large change, this patch would be a great band-aid.

Added a few test cases to validate the translation create, update and delete scenarios with the overridden permissions.

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request as a guide.

Removing the tests tag as they were added in #18

Will need a change record to announce the hook.

Added patch against #18 in 10.1 version

Patch in #25 doesnt contain all the changes present in patch from #18

Changes to file core/modules/content_translation/content_translation.api.php is missing in #25

I have hidden the patch in comment #25.

Maybe we should close this one in favor of Content translation access control
I've succesfully used that one to be able to provide entity access conditions on create translation, update translation or delete translation.
Without the need of an additional hook.

Create an MR with the patch from comment #18, on drupal 11.x the file core/modules/content_translation/tests/modules/content_translation_test/content_translation_test.module is not available.

As comment #30 said, we should decide what is the best option to control the access.

The Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

I have fixed the phpcs and phpstan errors.