Integrating TYPO3 9 Backend Modules: Linking Extensions

Frontend and Backend Development
1

How do I link two TYPO3 backend modules? Register each module separately and use the proper fluid link route.

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule(
    'Acme.modA',
    'sys_mod',
    'moduleA',
    '',
    [ 'AlphaCtrl' => 'runTask' ],
    [ 'access' => 'user,group', 'icon' => 'iconA', 'labels' => 'LLL:' ]
);

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule(
    'Acme.modB',
    'sys_mod2',
    'moduleB',
    '',
    [ 'BetaCtrl' => 'performAction' ],
    [ 'access' => 'user,group', 'icon' => 'iconB', 'labels' => 'LLL:' ]
);

<f:link.action action="performAction" controller="BetaCtrl" extensionName="modB">Switch Module</f:link.action>
2

In my experience, it is essential to ensure that both modules are registered under the correct parent categories and that the configuration options, especially the extensionName attribute and controller references, are consistent across both modules. Errors in linking often arise from mismatches between the module definitions and the fluid link’s parameters. Testing in a development environment helps pinpoint configuration issues quickly. Always consult the TYPO3 upgrade guide when moving between versions to avoid deprecated functions or alterations in the registration process.

3

hey jumpingbear, i noticed a smal mixing up in controller names can mess linking up. did anyone try tweaking rout names for a more fluid config? thas helped my project a lil bit, and i’m curious if someone found more uniqe workarounds

4

In my experience, ensuring that both modules are not only registered properly but also that the namespace conventions remain consistent across configurations is crucial for smooth integration of TYPO3 backend modules. I encountered issues when the settings in ext_localconf and fluid templates did not align, leading to unexpected errors. A rigorous review of the registration arrays and a clear mapping between controllers and actions are highly beneficial. In addition, leveraging TYPO3’s debugging tools to trace fluid link resolutions can provide deeper insights into the configuration process, thereby mitigating potential pitfalls.

5

hey jumpinbear, ive seen issues when keys and routes dont match exactly. try centralising your config and check for any misspelld names in module registration and fluid link. its a small tweak that helped me alot