TYPO3 Core

Jacob, could you provide some code / test extension to reproduce?

Hi Steffen,

Of course :-)

I have created a small extension in order to try out the new Extbase and ExtJS ExtDirect functionalities - so in my ext_localconf.php I have the following line, to enable my ExtDirect handler:

$TYPO3_CONF_VARS['SC_OPTIONS']['ExtDirect']['TYPO3.LbInquiry.Form'] = 'EXT:lbinquiry/Classes/Ajax/class.tx_lbinquiry_extdirect.php:tx_LbInquiry_extdirect';

And in my index controller of the test extension:

$GLOBALS['TSFE']->getPageRenderer()->addJsFile('?eID=ExtDirect&action=getAPI&namespace=TYPO3.LbInquiry', NULL, FALSE);

Which initializes tslib_ExtDirectEid->routeAction. In this method $GLOBALS['LANG'] are instantiated and initialized through the init() method, but the init() method requires a language key - which isn't supplied, nor is it possible from the frontend to send a language key, so unless the site only uses one language - it will be impossible to guess which language is needed.

A solution could be to take the same approach as tslib_eidtools::initLanguage() which supplies the string 'default' as default - although it would be nice to send some parameter to the ExtDirect router, which initializes the right language based on the page which is currently displayed.

The problem doesn't show up when using ExtDirect in backend modules, as it doesn't use the eID call, but instead the ajax.php script.

I have used the following wikipost as an inspiration: http://wiki.typo3.org/wiki/ExtDirect

Maybe you could attach that extension? Sorry for lazyness, I didn't dig into FE-ExtDirect, yet.

Sure - although I'll just make another sample, as this extension have dependencies to an unreleased extension

I've just uploaded a very simple example, it should be enough for testing

Acknowledged. There's no error visible (and no output except the <script> in the header), but the error is visible in TYPO3's Log.

The attached patch should fix the issue, but the language is still initialized with the default language. Please report your test results and afterwards I will add this patch to the core list.

I thought about a solution last night, and I think the best way to go, is to let the developer call tslib_eidtools::initLanguage() in the extdirect handler script instead of in the routeAction method.
By doing so, the developer has the freedom to select which language it going to be initialized - if he/she needs the language object.

AFAIK this must be initialized in an early state, because something in the initialization requires the language object. I will check that this night again and if it's like this, I will add the patch to the core list.

The initial patch is on the core list now. At least it will fix the warning for now. Any other improvements for the language detection can be added later on. However you always can reinstantiate the language object with the correct language in your own code for now.

Committed to rev. 10219.