Issue Bug Closed

#91558Auto slug update with multiple languages and editor language restrictions shows error

Chris Müller 06/03/20, 08:36 updated 11/15/26, 14:47

Description

In a website with multiple languages in a single tree there are four languages: en, de, pl, tr. An editor is restricted to only three languages: en, de, tr. When this editor now changes a page slug for, e.g., a “en” page, the following error is shown:

1: recordEditAccessInternals() check failed. [ERROR: Language was not allowed.]

However, the redirect is created, but is not working (see bug #91557).

Perhaps this bug is related to #84119.

This behavious was observed in TYPO3 10.4.3.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 6

  1. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-15T14:47:27+00:00" > 11/15/26, 14:47 </span>

    I checked this against the current main branch: the error still occurs, but its cause is not in EXT:redirects.

    A functional test with an editor who may only edit languages 0 and 1: page 2 and its sub page 5 are translated into languages 1 and 2. The editor changes only the slug of the default language page 2:

    • the slug of page 2 is saved, the sub page slug is updated and both redirects are created (t3://page?uid=…&_language=0)
    • the outer DataHandler reports Attempt to modify record pages:22 failed with: ERROR: Language was not allowed. (22 = translation of page 2 in language 2)
    • the DataHandler run of the SlugService for the sub page logs the same error for its translation in language 2

    The same happens with every save of a default language page by such an editor, without any slug change. The slug auto-update only makes it visible once more for every sub page that has such a translation. This is the problem described in #84119, see the analysis there.

    The broken redirect target mentioned above (#91557) was fixed separately via #89327.

    I am closing this issue as a duplicate of #84119