Content translation create access check with context for the target translation

Created on 13 July 2018, about 6 years ago
Updated 30 January 2023, over 1 year ago

Problem/Motivation

This is a follow-up of πŸ“Œ Introduce more flexible access control for content translation operations Needs work where @kfritsche mentioned in #2155787-22: Introduce more flexible access control for content translation operations β†’ that it would be useful to be able perform access checks for the translation create operation based on the target translation language.

Proposed resolution

Add a $context parameter to the access check methods and pass the language code of the target translation when checking the access for the translation create operation :

  • \Drupal\Core\Access\AccessibleInterface::access()
  • \Drupal\Core\Entity\EntityAccessControlHandlerInterface::access()

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Needs work

Version

10.1 ✨

Component
Content translationΒ  β†’

Last updated 1 day ago

No maintainer
Created by

πŸ‡©πŸ‡ͺGermany hchonov πŸ‡ͺπŸ‡ΊπŸ‡©πŸ‡ͺπŸ‡§πŸ‡¬

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

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

Production build 0.71.5 2024