Issue Bug Closed

#89550Localization of page fails without l10n_parent permission

Andreas Sturmberger 10/30/19, 17:27 updated 02/27/20, 12:42

Description

A non-Admin backenduser without having the “Transl.Orig (l10n_parent)” permission for the pages table can not localize pages.
It results in an “endless loading”.
The page gets inserted into the database with l10n_parent = 0 but is not shown in the backend.
If any user than tries to localize the page again, this error comes up:

Localization failed: there already are localizations (512) for language 2 of the “pages” record 92!

Therefore, a user without the l10n_parent permission should not be given the ability to localize pages, as it will result in inconsistent data.

The same error maybe also applies to other tables (tt_content, tx_*, ..), but i have not tested this.

Reviews 3