Feature #16563
closed
$typo_db_extLocalconf_script
0%
Description
It would be a very nice feature for developers and administrators if you could make it possible to define a variable in typo3conf/localconf.php containing the path to a php-file which would be included right after all the ext_localconf.php files from the extensions had been included.
This php-file should then contain settings that you would like to be certain to be set regardless of which extensions was installed.
This has already been implemented for ext_tables.php files via the
$typo_db_tables_script
in config_default.php
This variable may contain the name of a file in typo3conf/ which is included right after all the ext_tables.php files in extensions has been included.
(issue imported from #M4217)
Updated by Peter Niederlag over 17 years ago
I solve this with a simple:
'include_once('host_localconf.php');
very useful for synching installations beetween differnet hosts with differnet db-params et al...
IMO its not necessary to define an extra variable for this...
Updated by Mads Brunn over 17 years ago
But where would you insert this include-statement?
In an ext_localconf.php file? That wouldn't solve the problem because you need to be assured that this file is included AFTER all the other ext_localconf.php files.
Updated by Franz Holzinger over 17 years ago
It would be better to have a common setting like already done with
$typo_db_extTableDef_script = 'extTables.php';
This would make it easier to debug when all servers work the same.
Updated by Alexander Opitz over 10 years ago
- Category deleted (
Communication) - Status changed from New to Needs Feedback
- Target version deleted (
0) - PHP Version deleted (
4)
Hi,
as this issue is very old. Is this feature missing in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.