Core APIs

sorry for not being precise enough.

This is very similar to the TCA changes for wizards, where previously you specified a 'script' to the wizard, while you now specify a module name.

When registering a backend module you could specify a "navFrameScript" (either in old style $MCONF or in the addModule API call in ext_tables.php)

By doing so, the module will have an navigation iframe in addition to a content iframe and in the navigation iframe the URL specified for "navFrameScript" will be loaded.

The file list module still does it like this:

$MCONF['navFrameScript'] = '../../alt_file_navframe.php';

However, if you do not want to have an entry script for your navigation, but use a mod.php dispatched module action, until this change you had no way to register a navigation component. This is because mod.php dispatched modules need a CSRF token, which cannot be generated at registration time of the module (ext_tables.php loaded) as not no BE_USER is initialized to which the token can be bound to.

This:

    \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule(
        'TYPO3.CMS.' . $_EXTKEY,
        'help',
        'about',
        'top',
        array('About' => 'index'),
        array(
            'access' => 'user,group',
            'icon' => 'EXT:about/ext_icon.gif',
            'labels' => 'LLL:EXT:lang/locallang_mod_help_about.xlf',
            'navFrameScript' => BackendUtility::getModuleUrl('my_Mod')
        )
    );

does not work!

So I created a new way to register a navigation component:

    \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule(
        'TYPO3.CMS.' . $_EXTKEY,
        'help',
        'about',
        'top',
        array('About' => 'index'),
        array(
            'access' => 'user,group',
            'icon' => 'EXT:about/ext_icon.gif',
            'labels' => 'LLL:EXT:lang/locallang_mod_help_about.xlf',
            'navigationFrameModule' => 'my_Mod',
        )
    );

you just specify the module id and during rendering of the module menu, the URL for the navigation is generated.

I cannot answer the question where to put this information though, if we do not have documented the module registration API anywhere...

Hope this clears some things up

Thanks for all the details. At least the information is here and is not lost complete.

I guess Core API is the right manual, but there's no chapter about this currently. I guess it could be added here:

http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/MainClasses/UsefulFunctions/Index.html#typo3-cms-core-utility-extensionmanagementutility