Bug #89369
closedPage translations faulty when editor has no permissions for "l10n_parent"
0%
Description
- Create a site with the languages "Default" and "German"
- Create a page "Test" as admin in the default language.
- Create a backend user that is allowed to view and modify pages
- Do not give the user access permissions to the field "l10n_parent"
- Login as the backend user and try to translate the page
Expected result:
Page is translated
- A blank page is shown, the pagetree now infinitely shows the loading spinner
- If you try to translate the same page again, an error message is shown:
'"1: Localization failed: there already are localizations (5572) for language 20 of the "pages" record 885!"'
But the page translation is not visible in the list view. If you look into the db, the translation was inserted with the uid 5572, but l10n_parent is now 0, which should be the uid of the parent record.
This means, Datahandler is highly dependent on the backend users access permission to the l10n_parent field. If no permissions to this field exist, the newly created translation will be faulty.
- Do not allow translating a page if the backend user has no permissions for the field l10n_parent
- Or make the Datahandler not care about the access permissions to l10n_parent when translating a page.
Updated by Chris W almost 5 years ago
I can confirm this but in my case it is irrelevant if the editor has permissions for the field 'l10n_parent'.
Acutally editors in my TYPO3 9.5.11 projects are not able to create any translations at all.
Update
For me its wokring after i updated to TYPO3 9.5.13
Updated by Oliver Krammer almost 5 years ago
I can confirm that Bug with Typo3 9.5.13 if the User don't have the permission l10n_parent at the Pages table.
I can't repair it as Admin, i have to delete it in the Database.
Updated by Georg Ringer over 4 years ago
- Related to Bug #89672: Missing l10n_parent field permission breaks page translation process added
Updated by Georg Ringer over 4 years ago
- Status changed from New to Closed
thanks for creating this issue!
this is a duplicate of #89672 and solved in 10. therefore this has been closed.