TcaItemsProcessorFunctions

Read onlyYes

Various items processor functions, mainly used for special select fields in `be_users` and `be_groups`

Internal

This class is a hook implementation and is not part of the TYPO3 Core API.

Attributes
#[Autoconfigure]
$public: true

Table of Contents

Methods

__construct()  : mixed
populateAvailableCategoryFields()  : void
Populates a list of category fields (with the defined relationships) for the given table
populateAvailablePageTypes()  : void
populateAvailableTables()  : void
populateAvailableUserModules()  : void
populateCustomPermissionOptions()  : void
populateExcludeFields()  : void
populateExplicitAuthValues()  : void
getGroupedExcludeFields()  : array<string|int, mixed>
Returns an array with the exclude fields as defined in TCA and FlexForms Used for listing the exclude fields in be_groups forms.
getGroupedExplicitAuthFieldValues()  : array<string|int, mixed>
Returns an array with explicit allow fields.
getLanguageService()  : LanguageService
getRegisteredFlexForms()  : array<string|int, mixed>
Returns FlexForm data structures it finds. Used in select "special" for be_groups to set "exclude" flags for single flex form fields.

Methods

populateAvailableCategoryFields()

Populates a list of category fields (with the defined relationships) for the given table

public populateAvailableCategoryFields(array<string|int, mixed> &$fieldDefinition) : void
Parameters
$fieldDefinition : array<string|int, mixed>

populateAvailablePageTypes()

public populateAvailablePageTypes(array<string|int, mixed> &$fieldDefinition) : void
Parameters
$fieldDefinition : array<string|int, mixed>

populateAvailableTables()

public populateAvailableTables(array<string|int, mixed> &$fieldDefinition) : void
Parameters
$fieldDefinition : array<string|int, mixed>

populateAvailableUserModules()

public populateAvailableUserModules(array<string|int, mixed> &$fieldDefinition) : void
Parameters
$fieldDefinition : array<string|int, mixed>

populateCustomPermissionOptions()

public populateCustomPermissionOptions(array<string|int, mixed> &$fieldDefinition) : void
Parameters
$fieldDefinition : array<string|int, mixed>

populateExcludeFields()

public populateExcludeFields(array<string|int, mixed> &$fieldDefinition) : void
Parameters
$fieldDefinition : array<string|int, mixed>

populateExplicitAuthValues()

public populateExplicitAuthValues(array<string|int, mixed> &$fieldDefinition) : void
Parameters
$fieldDefinition : array<string|int, mixed>

getGroupedExcludeFields()

Returns an array with the exclude fields as defined in TCA and FlexForms Used for listing the exclude fields in be_groups forms.

protected getGroupedExcludeFields() : array<string|int, mixed>
Return values
array<string|int, mixed> —

Array of arrays with excludeFields (fieldName, table:fieldName) from TCA and FlexForms (fieldName, table:extKey;sheetName;fieldName)

getGroupedExplicitAuthFieldValues()

Returns an array with explicit allow fields.

protected getGroupedExplicitAuthFieldValues() : array<string|int, mixed>

Used for listing these field/value pairs in be_groups forms

Return values
array<string|int, mixed> —

Array with information from all of $GLOBALS['TCA']

getRegisteredFlexForms()

Returns FlexForm data structures it finds. Used in select "special" for be_groups to set "exclude" flags for single flex form fields.

protected getRegisteredFlexForms(string $table) : array<string|int, mixed>

This only finds flex forms registered in 'ds' config sections. This does not resolve other sophisticated flex form data structure references.

Parameters
$table : string

Table to handle

Tags
todo:

This approach is limited and doesn't find everything. It works for casual tt_content plugins, though:

todo:

The data structure identifier determination depends on data row, but we don't have all rows at hand here.

todo:

The code thus "guesses" some standard data structure identifier scenarios and tries to resolve those.

todo:

This guessing can not be solved in a good way. A general registry of "all" possible data structures is

todo:

probably not wanted, since that wouldn't work for truly dynamic DS calculations. Probably the only

todo:

thing we could do here is a hook to allow extensions declaring specific data structures to

todo:

allow backend admins to set exclude flags for certain fields in those cases.

Return values
array<string|int, mixed> —

Data structures


        

        
    




    

    

                            

            

                            
    

        On this page

        
    


            

                    

        

    

        

            
Search results