Bug #40112

Show warning on translation by user without access to "l18n_parent"

Added by Stefan Neufeind about 9 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
Start date:
2012-08-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

Situation:
  • user with limited rights, non-admin
  • no access to "Page Content: Transl.Orig (l18n_parent)" configured
  • but access to multiple languages

User chooses to localise an element (through page-view or list-view).

Result:
  • Content gets copied but still ends up in the original language, since TYPO3 is not allowed to write the l18n_parent.

While the result is correct imho this should raise some kind of warning towards the user so he knows why something does not work out as planned and can get to his admin to fix the rights.


Related issues

Related to TYPO3 Core - Bug #89672: Missing l10n_parent field permission breaks page translation processClosed2019-11-13

Actions
#1

Updated by Mathias Schreiber over 6 years ago

  • Target version set to 7.4 (Backend)
  • Is Regression set to No
#2

Updated by Susanne Moog about 6 years ago

  • Target version changed from 7.4 (Backend) to 7.5
#3

Updated by Benni Mack almost 6 years ago

  • Target version changed from 7.5 to 7 LTS
#4

Updated by Mathias Schreiber almost 6 years ago

  • Category set to DataHandler aka TCEmain
#5

Updated by Oliver Hader almost 4 years ago

  • Status changed from New to Accepted
  • Complexity set to medium

I guess we need to provide these meta information in fields that are disabled for a particular user / user-group differently when handling data.

#6

Updated by Benni Mack over 1 year ago

  • Related to Bug #89672: Missing l10n_parent field permission breaks page translation process added
#7

Updated by Christian Eßl over 1 year ago

There has been a fix for this recently:
https://forge.typo3.org/issues/89672

Is the problem described in the ticket still occuring?

#8

Updated by Riccardo De Contardi over 1 year ago

These are the results of my test with both TYPO3 9.5.14 and 10.4.0-dev

Prerequisites

  1. TYPO3 with two languages, ITA (default) and ENG (ID=1)
  2. an "Editors" BE usergroup and "Editor" BE user
  3. A page "test" with its own translation

TYPO3 10.4.0-dev

The BE Usergroup Access Control List for tt_content does not show Transl.Orig (l18n_parent) [tt_content:l18n_parent] so I guess that the issue can be considered solved for this version

TYPO3 9.5.14, Test 1

  1. on the BE Usergroup Access Control List for tt_content I unchecked Transl.Orig (l18n_parent) [tt_content:l18n_parent]
  2. Go to page "Test" and create a content element
  3. Page module > Languages > translate it with "Translate" mode and save

TYPO3 9.5.14, Test 2

  1. on the BE Usergroup Access Control List for tt_content I unchecked Transl.Orig (l18n_parent) [tt_content:l18n_parent]
  2. Go to page "Test" and create a content element
  3. List module > Click on the "Localize to" flag of the content element

Results

On both tests the translate content element is created with the right language (ENG), but its l18n_parent is still = 0

  • This means that the translated content element is created in "Copy" mode (free mode), so in this case "Connected Mode" and "Copy Mode" are the same

Can this issue be considered solved?

#9

Updated by Stefan Neufeind over 1 year ago

  • Status changed from Accepted to Resolved

Thanks for testing. Based on your tests I agree to declare it resolved. (I don't have an easy test-setup at hand myself now, but you tested it quite in-depth.)

#10

Updated by Benni Mack over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF