Bug #84119
open
Epic #90674: Backend UI not reflecting permissions
Limiting a BE-User to default language results in inconsistent saves.
Added by Marco Pfeiffer over 6 years ago.
Updated 23 days ago.
Description
scenario¶
I have a backend user who is only allowed to edit the default language.
This user now tries to edit a text media content element.
expected behavior¶
The user is able to save the content element.
What actually happens¶
The user gets this error:
recordEditAccessInternals() check failed. [ERROR: Language was not allowed.]
I assume this is because of the new copying behaviors. If I check the \TYPO3\CMS\Core\Authentication\BackendUserAuthentication::recordEditAccessInternals method, I see that all languages are checked for which a translation of the content element exists.
Workaround¶
I extended the BackendUserAuthentication class and removed that specific call to checkLanguageAccess. The other languages are still not visible but they could be edited now.
Files
I can confirm that (TYPO3 8.7.10).
- Status changed from New to Under Review
Does the element you try to edit and save need to be translated?
Yes, you'll need a content element that is translated to another language.
If a user now tries to edit the default version without having access to the translated version, then you'll get that error.
- Sprint Focus set to On Location Sprint
I can reproduce this problem in TYPO3 9.5.13.
The following scenario:
- Editor with language restrictions, for instance: languages "default" and "german"
- Editor tries to edit a tt_content element in "default" language.
- The content element can be translated to other languages the editor has no access permissions for.
The problem does not occur when editing localized records, only the default language is affected.
The process_datamap() function in DataHandler should probably not call "$this->BE_USER->recordEditAccessInternals($table, $id);" in this case.
I'm impressed that not more people had this problem over the course of 2 years. Am I missing something here?
- Category set to Localization
- Sprint Focus deleted (
On Location Sprint)
- Parent task set to #90674
- Related to Bug #91558: Auto slug update with multiple languages and editor language restrictions shows error added
- 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
The problem still occurs on TYPOe 9.5.28. Has anything happened since last year or are there any news regarding this problem?
The problem occurs also while saving the page properties in 10.4.17.
- Status changed from Under Review to New
I'm having the same problem with TYPO3 10.4.23 and the default language. Everything is set up correctly and with the provided patch, everything works fine. Can this topic be reopened, because with a multilanguage website and editors, who only have the right to edit specific languages, this is a must have!
I tested the issue again in TYPO3 11.
The issue described in the description is still occuring in 11.5.17.
However, if a backend user is restricted to non-default languages (language id != 0):
- they can see the default language elements, but can't edit them (correct)
- they can edit elements in their language (correct)
- they can hit the translate button, but the translations are made in the default language (not correct)
- they can add new elements in their language in mixed mode (correct)
- they can not add new elements in their language in connected mode (correct)
So yeah, language restricting editors is still broken in TYPO3 11
- TYPO3 Version changed from 8 to 11
- PHP Version deleted (
7.1)
- Related to Bug #93266: Backend-User restricted to language fails to edit tt_content records with inline relation added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 