Project

General

Profile

Actions
Copy link

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

Download all files
clipboard-202101111643-ykgiw.png (30.7 KB) clipboard-202101111643-ykgiw.png Anonymous, 2021-01-11 15:43
clipboard-202101111646-cko0w.png (25.1 KB) clipboard-202101111646-cko0w.png Anonymous, 2021-01-11 15:46
clipboard-202101111647-assn8.png (10.2 KB) clipboard-202101111647-assn8.png Anonymous, 2021-01-11 15:47

Related issues 3 (2 open — 1 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
Copy link
 #1

Updated by LUKA netconsult 12 months ago

We stumbled upon this problem in TYPO3 v12. It is caused by the feature "showPossibleLocalizationRecords" for inline Elements (TCA) https://docs.typo3.org/m/typo3/reference-tca/main/en-us/ColumnsConfig/Type/Inline/Properties/Appearance.html

If the Editor does not have access to the original language, this will throw an error. This beheaviour should be intercepted.

Our solution was, to simply deaktivate this feature.

Actions
Copy link
 #2

Updated by Georg Ringer 5 months ago

  • Sprint Focus set to Needs Decision
Actions
Copy link
 #3

Updated by Hannes Lau 4 months ago

  • Is duplicate of Bug #102625: "showPossibleLocalizationRecords" throws error if editor has no access to default language (Language was not allowed) added
Actions
Copy link
 #4

Updated by Hannes Lau 4 months ago

  • Status changed from New to Resolved
Actions
Copy link
 #5

Updated by Benni Mack about 1 month ago

  • Status changed from Resolved to Closed
Actions
Copy link
 #6

Updated by S P 21 days ago

  • Related to Bug #91900: Editor with language restriction to non-default language can't edit records of tables with inline fields configured with l10n_mode => exclude added
Actions
Copy link
 #7

Updated by S P 21 days ago

  • Related to Bug #84119: Limiting a BE-User to default language results in inconsistent saves. added
Actions
Copy link

Also available in: Atom PDF