Bug #93266
open![Author: Anonymous](/images/anonymous.png?1718153102)
Backend-User restricted to language fails to edit tt_content records with inline relation
0%
Description
Summary: Backend-User restricted to language fails to edit tt_content records with inline relation¶
Prerequisites:¶
- at least one additional language. In my example there is DEFAULT, EN and RU
- 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
Updated by LUKA netconsult 7 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.