[TYPO3-dev] Feature Request: Splitting localconf.php into hard

[Dennis Cheung]

Hi,

> Just imagine two possible solutions:
> 1. Build a hook, which includes localconf.php
> 2. Create a function in a class, which includes localconf.php. So this class could be XCLASSES.

No, hooks and xclasses should run AFTER localconf.php and extension's
ext_localconf.php area already been loaded.


>But then I have the problem, too, that I can change values over the
install-tool and have to manually check changes between
config_default.php and localconf.php

It is asking for default config, and that is the real default conifg.
I won't expect someone change the default by install-tool from an
typo3 instance.

It should be "flush the current config into default config" after did
the changes and confirmed works.

>>"NEVER touch the core."
I don't agree that. the more important is, you should know that you are doing.
Whatever touch the core or using the install-tool.


How about this?
 add just once more include("default_localconf.php") in config_default.php
 And you do copy (or symblic link?) the localconf.conf from an typo3 instance.

Dennis