Project

General

Profile

Actions

Bug #93266

closed

Backend-User restricted to language fails to edit tt_content records with inline relation

Added by Anonymous almost 4 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2021-01-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
Complexity:
Is Regression:
Sprint Focus:
Needs Decision

Description

Summary: Backend-User restricted to language fails to edit tt_content records with inline relation

Prerequisites:

  1. at least one additional language. In my example there is DEFAULT, EN and RU
  2. tt_content element ctype with inline relation

Configuration:

Backend-User "editor_russian" is restricted to language RU in its user-settings.

What happened?

Backend-User "editor_russion" tries to edit (just access - we are not talking about saving yet) a tt_content element with an inline relation (IRRE).

Sorry, you didn't have proper permissions to perform this change.
ERROR: Language was not allowed.

Cause:

BackendUserAuthentication.php calls checkLanguageAccess and fails.

But why?

Ghosts!

This kind of strange...

...it turned out, that "ghosts" are checked too!

Why are ghosts checked for language-access?

Is this really on purpose?


Files


Related issues 3 (2 open1 closed)

Related to TYPO3 Core - Bug #91900: Editor with language restriction to non-default language can't edit records of tables with inline fields configured with l10n_mode => excludeNew2020-07-30

Actions
Related to TYPO3 Core - Bug #84119: Limiting a BE-User to default language results in inconsistent saves.New2018-03-02

Actions
Is duplicate of TYPO3 Core - Bug #102625: "showPossibleLocalizationRecords" throws error if editor has no access to default language (Language was not allowed)Closed2023-12-07

Actions
Actions

Also available in: Atom PDF