[TYPO3-core] RFC: #15958: Bug: sections in flexforms require user to have access to default language

[Andreas Kiessling]

Hi,

On 23.11.2010 13:50, Tolleiv Nietsch wrote:
> Hi,
> haven't tested it yet, but this patch doesn't seem to respect the
> localization modes of flexforms. Dmitry is right such changes need to
> respect all localisation modes and I'd say that it might not be
> desireable that an editor is able to change the structure of an section.
>
> Cheers,
> Tolleiv


when langDisable is set to 1, then localization with a totally new 
content element can be assumed? If so, then the localized record needs a 
languageField and that is checked in the patch. Imho, an editor should 
be allowed to change the structure in this case, as it would not do 
anything to the default record.

The inline translation should only be done in an element with language 
set to 0 or -1?
I have modified the patch, so when the record has no language field or 
it is set to -1, access to default language is required.

The settings for langDisable and langChildren aren't passed to that 
function, but with the additional checks: are they needed?

You could of course localize a record that has a flexform field which 
has a setting of langDisable 0, but does that make sense at all?

I only want to let editors modify records that are in his allowed 
language. Right now, he can edit them, but not add new or remove 
unwanted sections that get automatically created when the record is 
localized.

Regards and thanks for the feedback,
Andreas
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 15958_v2.patch
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101123/428545bc/attachment.txt>