#93087Page Module "Translate" button not available if user can't edit default language
Description
If a BE user must be limited to only edit a not default language (s)he can’t use the Page Module “Translate” button because (s)he doesn’t have default language edit permission [allowed_languages].
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 4
-
Riccardo De Contardi changed category <span data-processor="relativetime" data-value="2021-03-30T21:01:50+00:00" > 03/30/21, 21:01 </span>
-
Georg Ringer commented and changed status
NewAccepted TYPO3 Version913 <span data-processor="relativetime" data-value="2025-04-01T21:43:46+00:00" > 04/01/25, 21:43 </span> -
Daniel Siepmann changed Duplicates #76274 Duplicates #95025 <span data-processor="relativetime" data-value="2025-05-27T06:59:04+00:00" > 05/27/25, 06:59 </span>
-
Oliver Bartsch commented and changed status
AcceptedClosed <span data-processor="relativetime" data-value="2026-10-26T08:24:34+00:00" > 10/26/26, 08:24 </span>Hey,
I checked this against current main. The part from the original report is solved: the “Translate” button in the page module now only needs modify rights for tt_content, a target language and untranslated content. It no longer checks access to the default language. The localization wizard also doesn’t require edit access to the default-language source records.
What’s still broken is what Georg described, and that is exactly “Translate does not work without access to the default language”. So I’m closing this one as a duplicate of #76274 and will continue there.
Cheers, Oli
still valid in v14. page localization works but the content elements end in the default language if localizing. creating free elements in language works.
what also is missing: the modal to select content elements which should be localized shows also elements with a type the editor might not has access. those can’t be localized. decision what to do: can those be localized even though permissions are not enough?