This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

Custom processing for mapping

A hook lets you create custom mapping markers:

name = {hookName|myCustomHook;param1|value1;param2|<cn>}


  • Your custom marker should be surrounded by opening and closing curly braces {...}.
  • Parameters are delimited by semi-colons (;).
  • A parameter is a pair of parameter name and parameter value delimited by a pipe (|).
  • First parameter should always be hookName.
  • Parameter value may contain references to LDAP attributes using the standard syntax with <>.


In your extension (in the ext_localconf.php file), register the hook using a code like:

        = 'EXT:extension/Path/To/Class/ClassName.php:VendorName\\ClassName';

where myCustomHook corresponds to one of the hookName parameters you use in your mapping.

Your class has to implement a method extraMerge which will receive the following arguments:

The name of the corresponding field in the mapping.
An array containing the current user/group record from TYPO3.
An array containing the current user/group record from LDAP.
An array containing LDAP attributes found in your mapping definition.
An associative array with all hook parameters found in your mapping definition (thus including hookName).

Your method should simply return a string for the value to be given to $field.