Bug #76274
openTranslate Button does not work when no Access to Default language
0%
Description
As a backend user with access to only 1 language the Translate-Button in the Page View does not work when the backend user have no rights for the default language (or any language from where the content is copied from).
The Translate button is there and the user can click it and select copy. No Errors are displayed. But the content does not get copied at all.
In the log the following message comes:
Attempt to copy record without having permissions to do so. [ERROR: Language was not allowed.].
Attempt to insert a record on page '[root-level]' (0) from table 'tt_content' without permissions. Or non-existing page. (msg#1.1.12)
Updated by Mona Muzaffar over 7 years ago
- Has duplicate Story #75699: i dont want to see the button "Translate" when i am not allowed to translate the content elements added
Updated by Riccardo De Contardi over 5 years ago
I tried the following test with TYPO3 9.5.8
Prerequisites¶
- Fresh TYPO3 installation with three additional languages:
- Italian (Default)
- English (ID=1)
- French (ID=2)
- German (ID=4)
- All the languages are configured in "Sites" Module
- BE usergroup with
- ACL: all fields, all tables selected
- Limit to Languages (
allowed_languages
): select only English and German
- Be user, assigned to the previous BE usergrop
Test Execution¶
- create a "Test" page
- translate it into all languages
- create two content elements in Default language
- translate only the first content element into all languages
- I always used "Translate" mode
- I always used Default as "starting" language
- make sure that "Editors" can see and edit the page
- switch user to "Editor"
- go to "Test" page
Test Results¶
in Page > "Languages" view
- the Editor can see Default, English and German "columns"
- The Default "column" cannot be edited, no "pencil" visible;
- this is also valid if you switch to "column" view: "Default" is selectable, but cannot be edited.
- you can still edit the page title with the pencil that pops up near it, but it leads to an error (shown twice):
1: recordEditAccessInternals() check failed. [ERROR: Language was not allowed.]
- It is possible to use the "translate" button, but the translation workflow does not complete! It is stuck at step 3 of 4!
I also tried with the following scenarios
- use "Copy" mode instead of "Translate" mode
- translate the first content element in German from English
but the result is the same, the translation does not finish.
Updated by leon jänicke over 1 year ago
- Related to Story #101564: User Interface related translation issues added