[TYPO3-core] RFC: #11019: User Setup Rewrite #4

[Rupert Germann]

hi

Steffen Kamper wrote:
>> 2. I don't like the idea of $GLOBALS['TUS']['ctrl']['hideFields'] - not
>> so much because it doesn't work in your patch (wrong var name used in
>> line 403: should be $fieldname instead of $field)
>> The more important reason is that in TCA all lists are whitelists
>> (showitem, showRecordFieldList) and you also use TUS->groups->fields so I
>> don't see a need to change this principle by introducing the first
>> blacklist. Why don't you use a property like 'exclude' for each field in
>> columns?
> 
> my idea was to use something you know from TS like
> TCEFORMS.table.field.disabled = 1. I would like to implement such TS
> later anyway.
> exclude for fields is for user access, i didn't looked yet for
> processing this.
> But you're right, this list is not needed as there is the positive list
> groups=>fields where a simple removal of one element is possible. Only
> disadvantage is that you may not know in which group the wanted field is.

why not making it even more TCA-like?
you could use the 'showitem' syntax to get rid of the complete TUS['groups']
part.

...
>> 5. simulateUser doesn't work anymore because you removed one
>> $GLOBALS['BE_USER'] to much (line 633)
>> 
> hm - i tested and it doesn't worked even before this patch. I fixed that
> too. Anyway this function works different too the UserAdmin->simulate.
> What is the purpose of that function, shouldn't it work same as the
> mentioned one with reload BE and exit-button on top?

no, not at all! 
The purpose of simulate user in 'user settings' module is to offer a fast
way to check and change some selected user settings on the fly _without_
reloading the complete BackEnd.

But reading the code would've told you the same ;-)

And with the new possibility to add more options to the settings module
(provided by your patch) this feature gets even more important.
 
greets
rupert