TYPO3 Core

Hi everybody,
I did some research for that bug and I have made the following two testcases:
Group1: LimitToLanguages nothing selected
- User 1: Limit to default language
- User 2: Limit to 2nd language

In this test case, the error occurs. I presume it happens because at the group level, nothing is selected.

If I use the following testcase:
Group1: Limit to default language
- User 1: Nothing selected
Group2: Limit to 2nd language
- User2: Nothing selected

it works as expected. I will check if I find the cause for this strange behavior.
Greets, Sebastian

I have to revise myself... It seems I had some error in my previous configuration.

I tested it again and again and I can not confirm the above issue.

I'd like to have more information on the issue, preferably a t3d export file.

Greets,
Sebastian

Is this bug related to #15114 ?

in testcase
- User 1: Limit to default language
- User 2: Limit to 2nd language

User2 can not edit CE with default language but he is able to delete it.

Hi,

testcase with 3 languages (english = default).
One user is related to language 3 (dutch) and he can´t edit the default language entries, but he is able to delete entries and to create new one.
TYPO3 Version 4.1.1

I cannot confirm the original bug description! A user, which is limited to the default language cannot edit records of another language, as they are hidden for him in the backend.

But I can confirm what Christian, Dimitry and Basti noted, which is the other way around. A user which is limited to a language (which is not default), can delete or move a record of the default language, but cannot hide/unhide or edit it.

So this is bug is somehow related to 0001678 as Christian already mentioned.

Any progress on this one?

Hey Helmut,

so if this bug is not reproducable and #15114 is now in the latest beta, I think we're all set here and can close this one?

Hey Benni,
I checked again, and still cannot reproduce the described issue. I would close this bug, since the original poster did not give any feedback. This was either no problem at all or got fixed by fixing #15114.

Unable to reproduce this issue with the latest trunk version.