[TYPO3-dev] Deploy localconf.php from test to live system

[Nicolas de Haen]

ext_localconf.php is loaded depending on 
$TYPO3_CONF_VARS['EXT']['extList']. So you can't change the 
$TYPO3_CONF_VARS['EXT']['extList']
and the $TYPO3_CONF_VARS['EXT']['extList_FE'] in the ext_localconf.php 
of an extension.

What we need is a possibility to define different extensionLists- 
especially since the ExtensionManager tries to load all extensions 
defined in the $TYPO3_CONF_VARS['EXT']['extList'] and if one doesn't 
exist Back- and Frontend are not working anymore.

Something like a $TYPO3_CONF_VARS['BE']['post_localconf'] could solve 
this problem:

Index: t3lib/config_default.php, Line 424

require(PATH_typo3conf.'localconf.php');

if(isset($TYPO3_CONF_VARS['BE']['post_localconf']) && 
@file_exists(PATH_typo3conf.$TYPO3_CONF_VARS['BE']['post_localconf']))
{
        require(PATH_typo3conf.$TYPO3_CONF_VARS['BE']['post_localconf']);
}

Patch attached.

Nico

Am 27.10.2010 23:59, schrieb Ernesto Baschny [cron IT]:
> Steffen Kamper schrieb am 27.10.2010 22:59:
>> Hi,
>>
>> why does noone comes up with a patch? It would be easy to implement a
>> logic to structure localconf like this:
>>
>> <?php
>> //put your preconfig here
>>
>> /*SYSTEM START*/
>> //this area will be used for write by core and install tool
>>
>> /*SYSTEM END*/
>>
>> //put your postconfig here
>
> IMHO no patch is needed. You already have a "START TOKEN" after which
> install tool puts his new lines into (see class.t3lib_install.php) and
> you also have your extensions ext_localconf.php where you can add stuff
> which will be loaded AFTER the localconf.php.
>
> So what's missing?
>
> Cheers,
> Ernesto
>