Issue Bug Closed

#83635Localized records with child records are not editable for Users limited to language

Andre Koller 01/22/18, 13:18 updated 10/22/26, 20:29

Description

This Bug is easy reproducible with the news-Extension.

1. Create a News record and add a related Link in Relations Tab with admin-User.
2. Translate the News record to second language (in my case german) with admin-User.
3. Delete the related Link in the localized News record with admin-User.
4. BE-User limited to language german can´t edit the translated News record.

Following Message appears:

Sorry, you didn't have proper permissions to perform this change.
ERROR: Language was not allowed.

I think it is not possible to show the related Link of the default language.

This Bug applies to all my Extension with IRRE Elements.

Reviews 1

History 57

  1. Andreas Wolf commented <span data-processor="relativetime" data-value="2018-01-23T21:57:48+00:00" > 01/23/18, 21:57 </span>

    I didn’t test it, but is this related to editing the record (= opening the form, that would be FormEngine), or saving it (= DataHandler)

  2. Oliver Hader commented and changed category <span data-processor="relativetime" data-value="2018-03-06T15:50:38+00:00" > 03/06/18, 15:50 </span>

    The error message being shown is a AccessDeniedException caught in EditDocumentController. This belongs to FormEngine…

  3. Gerrit Code Review pushed patch set 1 for master to change 57288 status New Under Review <span data-processor="relativetime" data-value="2018-06-21T14:34:16+00:00" > 06/21/18, 14:34 </span>

  4. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-22T20:29:17+00:00" > 10/22/26, 20:29 </span>

    This is fixed in the meantime by #102625 (commit 8d3b995d6f6, “Allow users w/o permissions on def lang to render CEs”).

    DatabaseUserPermissionCheck no longer runs the record edit access check for default language inline children shown in the context of a localized parent. Language restricted editors can therefore open the translation and see the untranslated default language children as placeholders instead of getting “ERROR: Language was not allowed.”.

    I verified this on current main with a functional test (language restricted backend user, translated parent without child, default language child still existing). It passes, and fails with the exact error from this report as soon as the check is applied again.

    Closing this issue as resolved.

    If this is still valid for you in v14, please open a new issue and provide information how to reproduce it. Thanks!